Bug 1475525

Summary:	[Docs][Director] Update the openstack baremetal node set command for UEFI to consider existing capabilities
Product:	Red Hat OpenStack	Reporter:	Jeremy <jmelvin>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	11.0 (Ocata)	CC:	bfournie, lbopf, mburns, rhos-maint, slinaber, srevivo
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
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:	2017-09-01 02:14:25 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:

Comment 6 Bob Fournier 2017-07-31 22:03:11 UTC

Jeremy - yes, this should be a doc bug, and it looks like Dan Mcpherson has made the update as noted on rhos-prio-list.

=================

 Jeremy,

Have updated the faulty commands:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/director_installation_and_usage/appe-alternative_boot_modes#appe-Alternative_Boot_Modes-UEFI

FYI, the "openstack baremetal node set" command required some bash-fu to change boot_mode without upsetting the existing capabilities. It should be a simple copy-paste of the command and replace <NODE NAME OR ID> with the node you want to set to uefi.

- Dan


==============

I have updated this to be a documentation bug.

Comment 7 Lucy Bopf 2017-09-01 02:14:25 UTC

Closing in response to comment 6, which states that the fix has been made.