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.

Description of problem:
the pxeloader option is not properly inherited from the parent host group and stays at 'no value'.

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

Steps to Reproduce:
1. create a host group, choose some OS and some PXEloader
2. create a nested host group and check its pxeloader option

Actual results:
Inherit (no value)

Expected results:
Inherit (the parent hg pxeloader value)

Created redmine issue http://projects.theforeman.org/issues/21426 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21426 has been resolved.

VERIFIED

Version Tested:
Satellite-6.3 Snap 28

steps:
1. Created hostgroup with OS and providing PXE loader
2. Created Nest hostgroup

Found PXE loader option inherited from its parent HG.

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/RHSA-2018:0336