Bug 1301627

Summary: rhel-osp-director: Scale-up Ceph from 1 to 3 fails, when Overcloud is deployed with SSL (resources.EndpointMap: Timed out) .
Product: Red Hat OpenStack Reporter: Giulio Fidente <gfidente>
Component: openstack-puppet-modulesAssignee: Emilien Macchi <emacchi>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: apevec, gfidente, lhh, mburns, ohochman, rhel-osp-director-maint, srevivo, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 7.0 (Kilo)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1299613 Environment:
Last Closed: 2016-01-25 15:12:40 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:

Description Giulio Fidente 2016-01-25 14:43:43 UTC 
+++ This bug was initially created as a clone of Bug #1299613 +++

rhel-osp-director:  Scale-up Ceph from 1 to 3 fails, when Overcloud is deployed with SSL (resources.EndpointMap: Timed out) .


Environment (backport-job 7.3):
------------------------------
instack-0.0.7-2.el7ost.noarch
instack-undercloud-2.1.2-37.el7ost.noarch
python-rdomanager-oscplugin-0.0.10-25.el7ost.noarch
python-heatclient-0.6.0-1.el7ost.noarch
openstack-heat-api-2015.1.2-6.el7ost.noarch
heat-cfntools-1.2.8-2.el7.noarch
openstack-heat-common-2015.1.2-6.el7ost.noarch
openstack-heat-engine-2015.1.2-6.el7ost.noarch
openstack-tripleo-heat-templates-0.8.6-103.el7ost.noarch
openstack-heat-templates-0-0.8.20150605git.el7ost.noarch
openstack-heat-api-cloudwatch-2015.1.2-6.el7ost.noarch
openstack-heat-api-cfn-2015.1.2-6.el7ost.noarch


Steps:
-------
(1) Deploy overcloud with SSL with 1 Ceph node.
(2) Attempt to Scale-up Ceph from 1 to 3 node 

Results :
---------
Stack Update failed - due to resources.EndpointMap: Timed out .
Comment 1 Giulio Fidente 2016-01-25 15:12:40 UTC 

*** This bug has been marked as a duplicate of bug 1301629 ***