Bug 1796191

Summary: Deploying with node specific overrides is error prone
Product: Red Hat OpenStack Reporter: Francesco Pantano <fpantano>
Component: openstack-tripleo-commonAssignee: Adriano Petrich <apetrich>
Status: CLOSED ERRATA QA Contact: David Rosenfeld <drosenfe>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: afariasa, amoralej, astupnik, gfidente, johfulto, mburns, mgarciac, nweinber, slinaber
Target Milestone: z12Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-8.7.1-20.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-24 11:33:20 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:
Bug Depends On:    
Bug Blocks: 1796197    

Description Francesco Pantano 2020-01-29 19:49:56 UTC 
Description of problem:

Using Node Specific Overrides to pass a different list of devices to a Ceph deployment [1] is error prone. The example in the doc embeds JSON in YAML. It's easy to make a simple mistake in the hand pasted JSON but not realize it until the deployment fails nearly an hour later.

It would be better if TripleO provided a simple utility to create a JSON environment file with NodeDataLookup set for all disks (except the root disk) found in introspection data. It could converts the output of `openstack baremetal introspection data save <node>` into a Heat environment file o be passed to `openstack overcloud deploy`.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 6 John Fulton 2020-03-02 15:07:26 UTC 
*** Bug 1805144 has been marked as a duplicate of this bug. ***
Comment 17 errata-xmlrpc 2020-06-24 11:33:20 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/RHBA-2020:2718