Description of problem: When changing the property Controller-1::count=3 and running heat stack-update, the update fails on the Controller resource with a very uninformative error messge: "FAILED due to None" Version-Release number of selected component (if applicable): openstack-tuskar-2013.2-dev18.g451f843.el7.centos.noarch python-tuskarclient-0.1.15.64-gc8e3799.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy a default overcloud with "instack-deploy-overcloud --tuskar" 2. Now change the controller count from 1 to 3: "tuskar plan-update -P Controller-1::count=3 <plan_id>" 3. Create the updated heat templates: "tuskar plan-templates -O tuskar_templates <plan_id>" 4. Run heat stack-update: "heat stack-update -f tuskar_templates/plan.yaml -e tuskar_templates/environment.yaml overcloud" Actual results: Stack update fails. Run the command "heat resource-show overcloud Controller" to see the reason: ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "None"
There is a much easier scenario to reproduce this bug. No need to have a default overcloud with 1 controller and then try to update it... You can already set the CONTROLSCALE parameter and install the overcloud right on the first time like this: export CONTROLSCALE=3 instack-deploy-overcloud --tuskar => You get the same error.
This also happens when using heat directly, without tuskar.
So this is an old bug (the way things go around here it is ancient). The CONTROLSCALE Udi refers to [1] is no longer being used. Today this corresponds to --control-scale [2]. I just tried it with 2 controls and still waiting but in any case I don't think this is a Tuskar issue (more specifically I don't think there is a problem with the way Tuskar handles the scaling). From chat today i see others have deployed the 3 controller scenario. Udi can we close this? Or are you still seeing an issue? [1] https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L98 [2] https://github.com/rdo-management/python-rdomanager-oscplugin/blob/master/rdomanager_oscplugin/v1/overcloud_deploy.py#L471
so we can close this right? i used the --control-scale 3 multiple times yesterday successfully
Moving to ON_QA to double check it based on Marios' comments.
Still a valid bug, see also https://bugzilla.redhat.com/show_bug.cgi?id=1233086
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.