Bug 1392428

Summary: OPS Tools | There is a typo in heat-templates that causes to keystone check not being executed on overcloud controllers.
Product: Red Hat OpenStack Reporter: Leonid Natapov <lnatapov>
Component: openstack-tripleo-heat-templatesAssignee: Martin Magr <mmagr>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: jschluet, mburns, mmagr, oblaut, rhel-osp-director-maint
Target Milestone: rcKeywords: Triaged
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-heat-templates-5.1.0-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 16:30:06 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 Leonid Natapov 2016-11-07 13:38:00 UTC
Description of problem:

There is a typo in heat-templates that causes to keystone check not being executed on overcloud controllers.

Typo is here: https://github.com/openstack/tripleo-heat-templates/search?utf8=%E2%9C%93&q=overcloud-kestone&type=Code

Kestone instead of Keystone.


override that either on environment file for overcloud deploy or in ansible playbook to use the typo instead.

Comment 1 Martin Magr 2016-11-08 08:44:08 UTC
This is not a blocker. Invalid default value in tripleo-heat-templates can be easily changed with two possible ways.

Comment 2 Jon Schlueter 2016-11-18 18:15:01 UTC
above mentioned patch has landed upstream/stable/newton and in OSP 10 build

Comment 4 Leonid Natapov 2016-11-29 13:12:27 UTC
Tested with openstack-tripleo-heat-templates-5.1.0-2.el7ost

typo is fixed.

Comment 6 errata-xmlrpc 2016-12-14 16:30:06 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.