Bug 1579198

Summary: [RHOS13][DOC] crudini package required for split stack deployment with overcloud node registration
Product: Red Hat OpenStack Reporter: Gurenko Alex <agurenko>
Component: openstack-tripleo-heat-templatesAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aschultz, emacchi, jschluet, jslagle, mburns, rhos-docs, srevivo
Target Milestone: rcKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-heat-templates-8.0.2-24.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1579197 Environment:
Last Closed: 2018-06-27 13:57:08 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:
Bug Depends On: 1579193, 1579197, 1581462    
Bug Blocks:    

Description Gurenko Alex 2018-05-17 07:06:32 UTC
+++ This bug was initially created as a clone of Bug #1579197 +++

+++ This bug was initially created as a clone of Bug #1579193 +++

Description of problem:

 Documentation does not mention that "crudini" package is required to be be installed on the overcloud node if overcloud node registration will be performed when doing split stack deployment.

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

How reproducible: 100%

Steps to Reproduce:
1. Do splistack deployment
2. Include yaml that will register overcloud nodes with CDN/SAT

Actual results: Deployment fails due to missing crudini package

Expected results: Deployment pass, but for that docs needs to include crudini package installation prior to deployment.

Additional info:

Comment 12 Gurenko Alex 2018-05-25 14:36:53 UTC
Verified on puddle 2018-05-25.1, deployment and registration completes successfully

Comment 15 errata-xmlrpc 2018-06-27 13:57:08 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.