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.
There is an existing step in Satellite Clone that disassociates the capsules Lifecycle Environments but it is run *after* the upgrade step. This step is super-critical as it prevents the cloned Satellite from syncing to the already existing Capsules in the source Sat->Capsule environment.
If this step does not get run, it is possible and likely due to Sync Plans, that the cloned Satellite may immediately start syncing to the Capsules in the source environment causing corruption and issues.
Rough Satellite Clone steps:
1) install sat bits via RPM
2) un-tar DBs
3) run satellite-installer --upgrade
4) hammer capsule disassociate
If step (3) fails, step (4) never gets run.
We need to be more proactive to ensure that this situation can't occur and have a step after (2) to either diassociate the LCEs or run some SQL to change the URL field for each capsule to point at a non-existent host (prepend with https://DISALBED- or something similar).
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