Bug 2134087

Summary:	[RFE] When changing a host's content source, auto-select the content source's synced LCE
Product:	Red Hat Satellite	Reporter:	Silas Pusateri <spusater>
Component:	Hosts - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	ahumbe, jlenz
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-17 15:46:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Silas Pusateri 2022-10-12 12:46:12 UTC

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:

Comment 1 Ashish Humbe 2022-10-14 15:33:27 UTC

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.

Comment 3 Jeremy Lenz 2023-03-17 15:46:47 UTC


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