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://127.0.0.1:5000/v2.0/ >/dev/null; do sleep 1; done'
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/sites-enabled/keystone.conf is missing. This gets created by devstack's lib/keystone during configure_keystone which grenade's upgrade-keystone does not call (correctly so). However, there is a bug in that devstack lib/keystone stop_keystone() function calls _cleanup_keystone_apache_wsgi(). Grenade does call stop_keystone during stop-base, deleting the original apache config but never re-generating it during upgrade.
Fix proposed to branch: master
Review: https:/