Bug 1384079

Summary: python-triploeclient dissregards ceph keys from envronemnt file
Product: Red Hat OpenStack Reporter: Giulio Fidente <gfidente>
Component: python-tripleoclientAssignee: Jiri Stransky <jstransk>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: afazekas, bengland, dmatthew, gfidente, gmeno, hbrock, jefbrown, johfulto, jomurphy, jschluet, jslagle, jstransk, jtaleric, mburns, mcornea, racedoro, rhel-osp-director-maint, sclewis, wusui
Target Milestone: rcKeywords: AutomationBlocker, Triaged
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-5.3.0-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 16:17:01 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: 1385034, 1388515    

Description Giulio Fidente 2016-10-12 13:37:23 UTC 
Description:

The CephClusterFSID and CephClientKey is ignored from my altered https://github.com/openstack/tripleo-heat-templates/blob/master/environments/puppet-ceph-external.yaml file.

The client generates a random CephClusterFSID, CephClientKey.

The /etc/ceph/* on the deployed nodes has a not working values,
the other values like GlanceRbdPoolName was respected from the same environment file.


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

python-tripleoclient.noarch      5.2.0-1.el7ost
Comment 7 Jiri Stransky 2016-10-18 10:55:14 UTC 
Replacing the patch link with stable/newton cherry pick.
Comment 8 Jiri Stransky 2016-10-19 11:08:40 UTC 
In stable/newton.
Comment 15 errata-xmlrpc 2016-12-14 16:17:01 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://rhn.redhat.com/errata/RHEA-2016-2948.html