Bug 2276926

Summary:	Hostgroup shows lifecycles and CV from every organizations irrespective of the Organization is selected in WebUI
Product:	Red Hat Satellite	Reporter:	Sayan Das <saydas>
Component:	Host Group	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.3	CC:	rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Regression, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:29:22 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 Sayan Das 2024-04-24 16:19:19 UTC

Description of problem:

When trying to create a new Hostgroup in Red Hat Satellite 6.14.3, It shows the library environment twice in the Lifecycle environment field, after selecting the Content Source. Depending on which Library entry I select, The list of CVs will change in the Content View field
I realized that it's perhaps related to the two Orgs I have but I see no reason for both the Library envs showing up there, while I am on a specific Org and Location context.

As a matter of fact, All Lifecycles from both Organizations show up in the Lifecycle Environment fields. 


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

Satellite 6.14.3

How reproducible:

Always


Steps to Reproduce:
1. Install a Satellite 6.14.3 and have two organizations created.
2. Login to UI and stay under a specific Organization
3. Go to Configure --> Hostgroups and create new HG
4. Select the Content Source
5. Click on the drop-down for Lifecycle Environment


Actual results:

Two library environments are listed


Expected results:

Only one Library environment will be listed for the Org i am sitting in. 

Additional info:

This does not happens for Hosts object. Upstream issue https://projects.theforeman.org/issues/37174

Comment 3 Partha Aji 2024-05-02 17:54:58 UTC

Connecting redmine issue https://projects.theforeman.org/issues/37174 from this bug

Comment 4 Eric Helms 2024-06-06 17:29:22 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.