Description of problem: Failed to remove lifecycle environments during capsules dissociation phase. Version-Release number of selected component (if applicable): 6.5 How reproducible: This issue observed with specific user's DB upgrade Steps to Reproduce: 1. Start Satellite clone operation for the specific user. 2. Observed some failed message's of lifecycle environments during capsule dissociation phase. 3. Satellite clone operation completed successfully. 4. Triggered foreman-maintain upgrade(foreman-maintain upgrade run --whitelist="disk-performance" --target-version 6.6 -y) to upgrade system from 6.5 to 6.6 and that was completed successfully. Actual results: Failed to remove lifecycle environments during capsules dissociation phase. [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] *** stdout: Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. Could not remove the lifecycle environment from the capsule: Lifecycle environment was not attached to the capsule; therefore, no changes were made. All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own. hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 11 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 11 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 12 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 12 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 9 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 9 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 7 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 7 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 10 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 10 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 8 --environment Library --organization XY_Z hammer -u admin -p ******* --csv capsule content add-lifecycle-environment --id 8 --environment Library --organization XY_Z Expected results: lifecycle environments should be removed successfully during capsules dissociation phase Additional info: This issue observed in very specific user DB upgrade.
merged in https://github.com/RedHatSatellite/satellite-clone/pull/363, but still needs to be released in a version
This bug has successfully verified in Sanp11. Capsule lifecycle environment properly dissociates during Satellite cloning.
Hi All, This Bugzilla has been successfully verified with 6.5.2. Logs are attached in the attachment. Thanks Devendra
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-2019:2364