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.

Created attachment 1132715 [details]
hostgroup doesn't retain association with content-source after submitting the form

Description of problem: I was trying to create a hostgroup and associated content-source. content-source was associated but as soon as I submitted the form and re-open it, the association with content-source auto removed. Ideally, it should retain.

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
hostgroup doesn't retain association with content-source after submitting the form

Expected results:


Additional info:

It turns out that this issue has been resolved upstream; however, it was not cloned to BZ.  Linking the bug to the upstream redmine and moving to POST.

Created a host group with a content source, and saved it. Content source was persisted correctly.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500