Bug 1437427

Summary: Updating services password results in errors
Product: Red Hat OpenStack Reporter: Gregory Charot <gcharot>
Component: puppet-tripleoAssignee: Angus Thomas <athomas>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: agurenko, aschultz, athomas, brault, dbecker, dcadzow, ealcaniz, gcharot, jcoufal, jjoyce, jschluet, mburns, morazi, ohochman, pablo.iranzo, rhel-osp-director-maint, shardy, skramaja, slinaber, smykhail, tvignaud
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-tripleo-5.5.0-14.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1468499 (view as bug list) Environment:
Last Closed: 2017-06-28 14:48:28 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: 1441944, 1468499    

Description Gregory Charot 2017-03-30 09:58:21 UTC
Description of problem:

When trying to update OSP services password, the deployment terminates in error.

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

OSP10 /OSP-d 10

How reproducible:

Always

Steps to Reproduce:
1. Deploy overcloud
2. Create a services_passwords.yaml file with new passwords [1]
3. Redeploy with -e services_passwords.yaml

Haven't try but the same should occur if 

1. Create a services_passwords.yaml file with custom passwords  
2. Deploy with -e services_passwords.yaml
2. update services_passwords.yaml file with new passwords [1]
3. Redeploy with -e services_passwords.yaml

Actual results:

Deployment terminates with error. [2]

Expected results:

Deployment terminates successfully + passwords updated.

Additional info:

Password are updated in the config files (checked in /etc on the ctrls).

This bug is very similar to [3], spotted by Steve Hardy, it seems like a fix is already available upstream. If confirmed, would it be possible to backport the path in OSP10 as this is our current long life release ?

A RH internal system with the current fail state is available to engineering if needed.

[1] http://pastebin.test.redhat.com/470178
[2] http://pastebin.test.redhat.com/470167
[3] https://bugs.launchpad.net/tripleo/+bug/1611704

Comment 1 Saravanan KR 2017-03-30 10:31:58 UTC
I have raised https://review.openstack.org/451742 in stable/newton to fix it.

Comment 7 Derek 2017-04-12 12:13:08 UTC
Discussed with the doc program manager, and we should be able to fit this in post OSP 11 GA.

Comment 8 Jaromir Coufal 2017-04-20 16:56:24 UTC
If we allow backport, is this already par of Ocata? So we don't introduce regression?

Comment 9 Alex Schultz 2017-04-20 19:07:02 UTC
Yea it's already in Ocata. https://review.openstack.org/#/c/451737

Comment 10 Jaromir Coufal 2017-04-22 20:02:07 UTC
Ack, +1 pm_ack on backport, needs dev and qe acks as well.

Comment 17 errata-xmlrpc 2017-06-28 14:48:28 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-2017:1585