Bug 1503834

Summary:	PXELoader not inherited from the parent host group
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Host Group	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Nikhil Kathole <nkathole>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bbuckingham, dlobatog, ehelms, inecas, kgaikwad, nkathole, pcreech, rplevka, tbrisker
Target Milestone:	Unspecified	Keywords:	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:	2018-02-21 17:01: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 Roman Plevka 2017-10-18 21:09:58 UTC

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)

Comment 4 Daniel Lobato Garcia 2017-10-23 13:42:26 UTC

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

Comment 5 Satellite Program 2017-10-27 08:04:22 UTC

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

Comment 6 Nikhil Kathole 2017-12-11 07:58:55 UTC

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.

Comment 8 Bryan Kearney 2018-02-21 17:01: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, 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