1. register a system: subscription-manager register ...
2. clean the system: subscription-manager clean
3. re-register w/ name: subscription-manager register --name name.example.com ...
4. check identity: subscription-manager identity -> name: name.example.com
5. check content hosts and note that only the first system is listed
Tom, isn't this by design now with 6.2 and the uniqueness constraint that we can only have a host with a name exist once within the Satellite?
Yes, it's true that there cannot be two hosts with the same name in any org on the server. However, should I be able to use --name w/ sub-mgr at all? If, for example, I spin up a local VM and register it to katello and its fqdn is katello.example.com but another dev has already registered with that name, what happens? Should I not be able to register w/ --name to pick a unique name, overriding fqdn?
If we're removing --name as an option, it should/could return an error to sub-mgr.
I am moving this from z to backlog since it's not a straightforward issue per #3. We can move it back to z if needed, once the questions in #3 are resolved.
*** Bug 1501212 has been marked as a duplicate of this bug. ***
Is this not a a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1376808 ?
*** Bug 1376808 has been marked as a duplicate of this bug. ***
I agree. Thanks! I happened to observe the same while doing some queries earlier this week. I closed bug 1376808 as a duplicate.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
*** Bug 1653330 has been marked as a duplicate of this bug. ***
I have a customer looking for this feature. They mentioned that the current `subscription-manager register --name <name-of-the-client>` command does not perform what it is expected to do.
So, either the name flag should be removed and documented, or it should do what it says it will in the documentation.
Can someone review and confirm?
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Wrond closure reason.
*** Bug 1843591 has been marked as a duplicate of this bug. ***