Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1345980

Summary: Regression - unable to deploy without controller
Product: Red Hat OpenStack Reporter: Cyril Lopez <cylopez>
Component: openstack-tripleo-heat-templatesAssignee: Steven Hardy <shardy>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: agurenko, athomas, dbecker, dmaley, ealcaniz, hjensas, jcoufal, lhh, mburns, morazi, pablo.iranzo, rhel-osp-director-maint, roxenham, shardy, vcojot
Target Milestone: asyncKeywords: OtherQA, Regression, Reopened
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-0.8.14-17.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1365679 (view as bug list) Environment:
Last Closed: 2016-08-31 17:39:59 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: 1347518, 1365679    

Description Cyril Lopez 2016-06-13 15:02:35 UTC
Description of problem:
In OSP-d 7.x, we was able to spawn a stack without Controller with success in case of you provide the puppet variable needed

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.14-11.el7ost.noarch

How reproducible:

time openstack overcloud deploy \
--templates templates/ \
-t 120 \
--control-scale 0 \
--compute-scale 1 \
--ceph-storage-scale 0 \
--block-storage-scale 0 \
--swift-storage-scale 0 \
[...]

Steps to Reproduce:
1. Try to deploy

Actual results:
Deploying templates in the directory /usr/share/openstack-tripleo-heat-templates
ERROR: Parameter 'ControllerCount' is invalid: 0 is out of range (min: 1, max: None)



Additional info:
Fix it with this patch
--- /usr/share/openstack-tripleo-heat-templates/overcloud.yaml  2016-05-10 15:31:19.000000000 -0400
+++ overcloud.yaml      2016-06-13 10:48:40.254967549 -0400
@@ -385,7 +385,7 @@
     type: number
     default: 1
     constraints:
-      - range: {min: 1}
+      - range: {min: 0}
   controllerExtraConfig:
     default: {}
     description: |

Comment 1 Mike Orazi 2016-06-13 15:47:06 UTC
I believe this is operating as intended to avoid folks from accidentally creating a cloud with no control plane.

Can you describe the use case where this type of behavior is desirable?

Comment 2 Jaromir Coufal 2016-06-13 15:50:55 UTC
Hi Cyril. The original behavior was more a bug since we never supported deployments without Control plane. If this is needed, we would need to gather requirements and use cases and add it as an RFE request for future release. Please send me an e-mail with more info if we there is a need for this feature.

Comment 4 Edu Alcaniz 2016-07-20 09:13:41 UTC
This impact in the project of the customer. We need this RFE or workaround.

Comment 7 Steven Hardy 2016-07-20 11:03:24 UTC
I just posted this patch upstream:

https://review.openstack.org/344739

It partially reverts this patch:

https://review.openstack.org/#/q/Ib4917843f3e4770f0260db72719ed6af0ee8dc13

Where I added the contraint to ensure at least one controller, otherwise there's no control plane and the resulting deployment isn't functional.

Clearly this use-case isn't what we expected, but I see no reason to enforce that contraint if it's causing problems.

Comment 8 Steven Hardy 2016-07-20 11:11:23 UTC
Upstream bug https://bugs.launchpad.net/tripleo/+bug/1604777

Comment 20 errata-xmlrpc 2016-08-31 17:39:59 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/RHBA-2016-1786.html