Bug 2279315

Summary:	Hostgroup not showing associated Kickstart Repository in edit
Product:	Red Hat Satellite	Reporter:	Odilon Sousa <osousa>
Component:	Host Group	Assignee:	Partha Aji <paji>
Status:	CLOSED MIGRATED	QA Contact:	Pavel Novotny <pnovotny>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	ahumbe, fperalta, jlenz, osousa, pnovotny, rlavi
Target Milestone:	6.15.1	Keywords:	MigratedToJIRA, Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-4.11.0.11-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2265396	Environment:
Last Closed:	2024-06-06 17:37:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Pavel Novotny 2024-05-23 20:17:07 UTC

Verified in Satellite 6.15.1 snap 1:
satellite-6.15.1-1.el8sat.noarch
rubygem-katello-4.11.0.12-1.el8sat.noarch

Verified by following the reproducer in comment 0:
> 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

Result:
When editing the hostgroup, the assigned kickstart repository is displayed in the Synced Content field.

Comment 3 Eric Helms 2024-06-06 17:37:15 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.