Failed to remove lifecycle environments during capsules dissociation phase.

[devendra104]

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

[devendra104]

@johnpmitsch This issue does not occur for all DB upgrade, it happens for one.
Is it expected or related to the cloning issue?