Bug 1718904

Summary: Cannot create hostgroup associated with content source id=1 and LFE id=1
Product: Red Hat Satellite Reporter: Lukas Pramuk <lpramuk>
Component: Host GroupAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: inecas, kgaikwad
Target Milestone: 6.6.0Keywords: 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: Environment:
Last Closed: 2019-06-14 13:35:30 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 Lukas Pramuk 2019-06-10 14:15:21 UTC 
Description of problem:
Cannot create hostgroup associated with content source id=1 and LFE id=1 (Default Organization's Library) 

(x) Unable to save
The selected content source and lifecycle environment do not match

While other organizations' Libraries (id<>1) or other LFEs (id<>1) of the Default Organization are ok to match default content source (id=1)

This is regression against 6.5

Version-Release number of selected component (if applicable):
satellite-6.6.0-5.beta.el7sat.noarch
foreman-1.22.0-0.5.RC2.1.el7sat.noarch
katello-3.12.0-0.5.master.el7sat.noarch

How reproducible:
deterministic

Steps to Reproduce:
1.
 # hammer hostgroup create --name hg_library --lifecycle-environment-id 1 --content-source-id 1
Could not create the hostgroup:
  The selected content source and lifecycle environment do not match

while
 
# hammer hostgroup create --name hg_dev --lifecycle-environment-id 2 --content-source-id 1
Hostgroup created.


Actual results:
Default Organization's Library (with id=1) is problematic when creating hostgroup

Expected results:
Default Organization's Library works as other LFEs in regards to hostgroup creation
Comment 4 Brad Buckingham 2019-06-14 13:35:30 UTC 
This appears to be a duplicate of bug 1713248; therefore, closing.  Please feel free to re-open if there are any concerns.

*** This bug has been marked as a duplicate of bug 1713248 ***