Bug 1314268

Summary: hostgroup doesn't retain association with content-source
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: Host GroupAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED ERRATA QA Contact: Stephen Benjamin <stbenjam>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, stbenjam
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/13860
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:04:13 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:
Attachments:
Description Flags
hostgroup doesn't retain association with content-source after submitting the form none

Description Sachin Ghai 2016-03-03 10:15:32 UTC
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:

Comment 2 Brad Buckingham 2016-03-08 18:16:59 UTC
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.

Comment 3 Stephen Benjamin 2016-03-24 15:51:11 UTC
Created a host group with a content source, and saved it. Content source was persisted correctly.

Comment 6 errata-xmlrpc 2016-07-27 09:04:13 UTC
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