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).
This was fixed by https://github.com/RedHatSatellite/satellite-clone/pull/230
Verified in satellite-clone-1.2.1-1.el7sat.noarch. If the `satellite-installer --upgrade` failed, capsule is disassociated before the playbook stops..
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