Bug 1329719

Summary: DOC: 5.4. Defining the Root Disk for Nodes - steps no longer work
Product: Red Hat OpenStack Reporter: Chris Janiszewski <cjanisze>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED DUPLICATE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: dmacpher, srevivo
Target Milestone: ---Keywords: Documentation, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-26 02:14:32 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:

Description Chris Janiszewski 2016-04-22 17:15:59 UTC
Description of problem:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/director-installation-and-usage/54-defining-the-root-disk-for-nodes

DOC: 5.4. Defining the Root Disk for Nodes - steps no longer work


Version-Release number of selected component (if applicable):
RH OSP 8

How reproducible:

After invoking on udercloud:
for uuid in `ironic node-list | awk '{print $2}'`; do echo "Node ID: $uuid"; ironic node-show $uuid | grep 'properties\|extra ' -A3; done

it no longer shows multiple drives attached to a system. Hence there is no way to verify serial number of the drive in make the drive a default for boot.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
This used to work in RHEL OSP 7

Additional info:

We need to fix this functionality - there definitely a need for assigning which drive in multi-drive environment should be used for OS/boot, but also a document need to be adjusted to reflect any changes in RH OSP 8 ... This used to work in RHEL OSP 7

Comment 2 Dan Macpherson 2016-04-26 02:14:32 UTC
Closing this BZ as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1330220 which also contains the correct commands.

*** This bug has been marked as a duplicate of bug 1330220 ***