Bug 1523059 - Existing PXE based provisioning will break after 6.3 upgrade if "PXE loader" is set to none
Summary: Existing PXE based provisioning will break after 6.3 upgrade if "PXE loader" ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Upgrading and Updating Red Hat Satellite
Version: 6.3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Melanie Corr
QA Contact: Russell Dickenson
URL:
Whiteboard:
: 1527007 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-07 06:29 UTC by Ranjan Kumar
Modified: 2019-09-26 16:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 00:26:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1392230 0 medium CLOSED [RFE] [6.3] Incorporate UEFI documentation for Satellite 6.3 2021-02-22 00:41:40 UTC

Internal Links: 1392230

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. ***
Note You need to log in before you can comment on or make changes to this bug.