Bug 1319753 - The director should not set Ceph's cluster FSID as the rbd secret id
Summary: The director should not set Ceph's cluster FSID as the rbd secret id
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Alan Bishop
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 12:33 UTC by Yogev Rabl
Modified: 2018-01-31 13:43 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-31 13:43:48 UTC
Target Upstream Version:
gfidente: needinfo? (yrabl)
scohen: needinfo-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yogev Rabl 2016-03-21 12:33:47 UTC 
Description of problem:

The Nova and Cinder services require a random uuid as a secret key to connect the volumes and disks to the instances, as good practice, the uuid should not be shared and random. 
Furthermore, every Ceph cluster have its own ID, a random uuid. 

The Director uses the same uuid in both cases.  


Version-Release number of selected component (if applicable):
openstack-tripleo-puppet-elements-0.0.4-1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. deploy overcloud with external Ceph

Actual results:
The secret uuid of used by Nova and Cinder is the same as Ceph's FSID

Expected results:
The uuid is been generate randomly without any correlation with any other Ceph parameter
Comment 2 Emilien Macchi 2016-05-16 15:32:59 UTC 
Moving the bug from Puppet to TripleO, where the actual fix will be done.
Note You need to log in before you can comment on or make changes to this bug.