Bug 1523059

Summary:	Existing PXE based provisioning will break after 6.3 upgrade if "PXE loader" is set to none
Product:	Red Hat Satellite	Reporter:	Ranjan Kumar <rankumar>
Component:	Docs Upgrading and Updating Red Hat Satellite	Assignee:	Melanie Corr <mcorr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Russell Dickenson <rdickens>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3.0	CC:	adahms, mcorr, mdekan, rdickens
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 00:26: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 Ranjan Kumar 2017-12-07 06:29:59 UTC

There should be a note in upgrade documents that after upgrade "PXE loader" should be to "PXELinux BIOS" or based on provisioning method. 


An end user when trying to provision machines after upgrade would only see the default PXE menu, however there is a new option introduced in 6.3 called "PXELinux BIOS" and "PXELinux UEFI" depending on the provisioning requirement. These values are by default set to none. So, an additional setup for the end user would be to set these values after upgrade.

Comment 4 Andrew Dahms 2017-12-11 00:03:41 UTC

Assigning Russell as the QA contact.

Russell - could you take a look at the changes for this bug?

Comment 5 Stephen Wadeley 2017-12-11 08:40:32 UTC

(In reply to Andrew Dahms from comment #4)
> Assigning Russell as the QA contact.
> 
> Russell - could you take a look at the changes for this bug?

and fell free to change the QA contact.

Comment 8 Andrew Dahms 2018-01-16 00:18:27 UTC

Updating the doc type.

Comment 9 Ivan Necas 2018-01-17 12:00:20 UTC

*** Bug 1527007 has been marked as a duplicate of this bug. ***