issues registering with subscription for clones created from parent registered with classic

Posted on

Scenario. Master Image VMs which are registered using rhn-register being used to clone child servers who we want to register with subscription manager. The server is cloned and comes up 'thinking' it is registered. we don't want to de-register it before changing its name because then the parent image would no longer be registered. What is the proper process for removing traces of the parent's registration from the cloned server. After that what is the proper process for getting the new server set up with subscription manager?

currently our process is : subscription-manager register --autosubscribe

but from what i have seen that isn't enough. i tried "subscription-manager attach --auto" but it told me that there weren't any installed productions

"subscription-manager attach --pool=XYZ01234567" works but we aren't sure how to tell which subscriptions should be used for which servers and are afraid of what will happen if we attach one that has software that isn't installed, will it try to install that software onto the server

I found "subscription-manager register --username admin-example --password secret --auto-attach"m but haven't tried it yet as i am thinking the problem may be the pieces of the original install that are still on the clone.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.