Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
If you have register_to_portal commented out, you have to use an activation key and org (in the top of satellite-clone-vars.yml). The details around this are documented under the section titled "required variables"
Do you have this filled in?
Comment 2Christian Marineau
2017-12-30 16:25:57 UTC
I think we should make sure to prioritize the following BZ which would prevent this situation. Satellite Installation Guides are never stipulating to use Activation Key, thus the registration is expected to have been done manually so we should not be having to explicitly change the variable.
https://bugzilla.redhat.com/show_bug.cgi?id=1519515
Comment 6sthirugn@redhat.com
2018-01-15 20:20:46 UTC
*** Bug 1527288 has been marked as a duplicate of this bug. ***
Comment 7sthirugn@redhat.com
2018-02-01 18:36:47 UTC
Verified in satellite-clone-1.2.1-1.el7sat.noarch
Now the default behavior is manual registration to portal. The default workflow is:
1. Manually register to portal and attach right subscriptions
2. copy backup files
3. install satellite-clone
4. Run satellite-clone
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0330