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.

Description of problem: When changing a hosts content source from one capsule to another it is difficult to determine which LCE is synced on which capsule which leads to errors during updating


Version-Release number of selected component (if applicable):
6.12.0

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
A warning that the LCE that is assigned and synced is different than the host's current

Additional info:

Recreation steps: 

Create LifeCycleEnv1 and assign it to Capsule1
Create LifeCycleEnv2 and assign it to Capsule2

Create CV1 and publish/promote Version 1 to LifeCycleEnv1, 
Create CV2 and publish/promote Version 1 to LifeCycleEnv2. 

Register Client1 via Capsule1, and assign CV1 to the client system.

Go to All Hosts -> Host profile -> Click on "Change Content Source" 
Set 

Environment = LifeCycleEnv1
Content View = CV1
Content Source = Capsule2 

Click on "Change Content Source" 

If LifeCycleEnv1 is not synced on the Capsule2 we should not be able to select while changing the content source.

*** This bug has been marked as a duplicate of bug 1944710 ***