grenade fails to upgrade keystone when mod wsgi is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Chmouel Boudjnah | ||
grenade |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Working on sideways upgrades within juno. Since icehouse, devstack has enabled mod wsgi services by default, including keystone. Attempting to run grenade within a release fails with a keystone start error:
2014-09-03 05:44:41.967 | Waiting for keystone to start...
2014-09-03 05:44:41.967 | + timeout 120 sh -c 'while ! curl --noproxy '\''*'\'' -k -s http://
2014-09-03 05:46:41.970 | + die 489 'keystone did not start'
2014-09-03 05:46:41.970 | + local exitcode=0
2014-09-03 05:46:41.970 | [Call Trace]
Reproducing locally, I get a connection refused and it looks like /etc/apache2/
Changed in grenade: | |
status: | In Progress → Invalid |
Changed in devstack: | |
assignee: | nobody → Chmouel Boudjnah (chmouel) |
Fix proposed to branch: master /review. openstack. org/118742
Review: https:/