Updating change-hostname to suggest using global registration #9591
Conversation
|
Can one of the admins verify this patch? |
2 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
| @@ -140,18 +140,15 @@ def next_steps_message | |||
| else | |||
| # the following multi-line string isn't indented because the indents are taken literally. | |||
| %( | |||
| You will have to install the new bootstrap rpm and reregister all clients and #{@plural_proxy} with subscription-manager | |||
| (update organization and environment arguments appropriately): | |||
| You will have to reregister all clients and #{@plural_proxy} with the Satellite server. | |||
There was a problem hiding this comment.
We don't use Satellite in upstream, but I'm not sure if we even handle branding at all.
There was a problem hiding this comment.
Haha good point I should avoid saying Satellite in this.
|
|
||
| subscription-manager refresh | ||
| yum repolist | ||
| For each client and #{@plural_proxy}, go to Hosts > Register Host in the Satellite UI. |
There was a problem hiding this comment.
I think this is a poor experience. Users can't script this and if you have 100s or 1000s of hosts it's not going to be acceptable.
IMHO we should have a remote execution job that updates the registration instead. Then we can tell users it can be called via Hammer as well.
There was a problem hiding this comment.
I'm not the expert here, so I would like to see if there's already other ways to achieve what you're talking about. If not, then we should spend time creating a solution like you described.
Griffin-Sullivan
force-pushed
the
rpm/develop
branch
from
feabc4c to
143d5a7
Compare
|
@ares I was told your opinion would be helpful here as well |
No description provided.