Bug 1718904 - Cannot create hostgroup associated with content source id=1 and LFE id=1
Summary: Cannot create hostgroup associated with content source id=1 and LFE id=1
Keywords:
Status: CLOSED DUPLICATE of bug 1713248
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-10 14:15 UTC by Lukas Pramuk
Modified: 2019-06-14 13:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 13:35:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.