Failed deployment due to Hiera resolution of keystone::wsgi::apache::workers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiri Tomasek |
Bug Description
Overcloud Controller deployments fail due to not being able to resolve the value of keystone:
Specifying a literal integer value (e.g. 11) in the Template or Plan instead of the default variable of %{::processorcount} produces a successful deployment.
[stack@
+------
| Field | Value |
+------
| id | 16240e1f-
| server_id | 3fa46f14-
| config_id | 93462543-
| creation_time | 2016-10-
| updated_time | 2016-10-
| status | FAILED |
| status_reason | deploy_status_code : Deployment exited with non-zero status code: 1 |
| input_values | {u'step': 1, u'update_
| action | CREATE |
| output_values | {u'deploy_stdout': u"Matching apachectl 'Server version: Apache/2.4.6 (Red Hat Enterprise Linux)\nServer built: Aug 3 2016 08:33:27'\n", u'deploy_stderr': u"exception: connect failed\
| | 'tripleo:
| | looking up 'tripleo:
+------
[stack@
---
[heat-admin@
keystone:
[heat-admin@
Changed in tripleo: | |
assignee: | nobody → Jiri Tomasek (jtomasek) |
I've also seen this (deploying master from the UI), setting Priority to High as it makes the deployment fail. (It's also not obvious to debug, with the error focusing on trusted_cas).