Bug 2265396

Summary:	Hostgroup not showing associated Kickstart Repository in edit
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Host Group	Assignee:	Partha Aji <paji>
Status:	CLOSED MIGRATED	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	ahumbe, fperalta, jlenz, osousa, rlavi
Target Milestone:	stream	Keywords:	MigratedToJIRA, Regression, Triaged
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:
Clones:	2272115 2279315 (view as bug list)		Environment:
Last Closed:	2024-06-06 17:04:11 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 Partha Aji 2024-02-21 20:33:03 UTC

Description of problem:
Create a hostgroup with a KS repository and save. Go to edit it and notice the ks group is not displayed (even though it is in the database)

Version-Release number of selected component (if applicable):
6.15,6.14 (might be in 6.13 also...)

How reproducible: always


Steps to Reproduce:
1. Sync a kickstart repository ks-zoo (I synced => https://partha.fedorapeople.org/test-repos/kickstart-zoo/)
2. Create a hostgroup with Library/Default Org View/x86_64/Redhat-7/ks-zoo in synced content.
3. Save the hostgroup
4. Click on the hostgroup again and go to Operating System tab


Actual results:
Notice that Synced Content is not populated

Expected results:
Synced Content should be showing ks-zoo

Additional info:

If you looked at the content facet of the host group in rails console you clearly see that the KS repo is actually set. Its just not populated in the dropdown

Comment 1 Partha Aji 2024-02-21 20:58:40 UTC

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

Comment 2 Bryan Kearney 2024-02-22 00:04:08 UTC

Upstream bug assigned to paji

Comment 3 Bryan Kearney 2024-02-22 00:04:10 UTC

Upstream bug assigned to paji

Comment 4 Bryan Kearney 2024-03-06 20:03:36 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37197 has been resolved.

Comment 7 Jeremy Lenz 2024-03-18 17:44:35 UTC

A (somewhat clunky) workaround: If you go to create a host using this hostgroup, the form will correctly show the kickstart repository that the new host would inherit from the hostgroup.

Comment 8 Peter Ondrejka 2024-04-15 11:27:21 UTC

Verified on Satellite stream snap 54

Comment 9 Eric Helms 2024-06-06 17:04:11 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.

Comment 10 Red Hat Bugzilla 2024-10-05 04:27:20 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days