Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1751981

Summary: Parent object properties are not propagated to Child objects in Location and Host Group
Product: Red Hat Satellite Reporter: Marco Verschuur <marco.verschuur>
Component: Host GroupAssignee: Ondřej Ezr <oezr>
Status: CLOSED ERRATA QA Contact: Mirek Długosz <mzalewsk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: egolov, inecas, kgaikwad
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: foreman-2.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:02 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 Marco Verschuur 2019-09-13 10:58:52 UTC
Description of problem:
In a Parent-Child relation (e.q. in Location and Host Group) the Parent properties are not being propagated to the Child objects.

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


How reproducible:
Consistent

Steps to Reproduce:
1.Create Parent Location with Subnet assigned
2.Create a Child Location from this Parent
3.Create a host and assign it to the Child Location

Actual results:
Error message: Subnet not defined for host's location
(this happens both via GUI's "Create Host" and hammer-cli 'hammer host create --name <name> --location <Child Location>...'

Expected results:
Host created successfully with assigned Location's properties

Additional info:
Related to bug #1733241 where hammer doesn't support inheritance properties.

Comment 3 Marek Hulan 2019-09-24 09:02:34 UTC
Created redmine issue https://projects.theforeman.org/issues/27927 from this bug

Comment 4 Bryan Kearney 2019-11-25 03:02:11 UTC
Upstream bug assigned to oezr

Comment 5 Bryan Kearney 2019-11-25 03:02:13 UTC
Upstream bug assigned to oezr

Comment 6 Bryan Kearney 2019-11-26 15:03:47 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27927 has been resolved.

Comment 7 Mirek Długosz 2020-06-30 10:25:34 UTC
Host assigned to child location can be created using both UI and CLI.

Tested on:
Satellite 6.8.0 snap 6
katello-3.16.0-0.3.rc3.el7sat.noarch
satellite-6.8.0-0.6.beta.el7sat.noarch
foreman-2.1.0-0.22.rc3.el7sat.noarch
pulp-server-2.21.2-1.el7sat.noarch

Comment 10 errata-xmlrpc 2020-10-27 12:59:02 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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366