doing a clean.sh / stack.sh cycle with USE_SSL=True was failing
because we were no longer cleaning up the keystone site fully, so some
of the early mod_ssl queries hit an invalid apache configuration.
Change-Id: Ic6f3f601e532ec50c0234d928c25b378d9e95e32
| ... | ... |
@@ -25,7 +25,6 @@ |
| 25 | 25 |
# - create_keystone_accounts |
| 26 | 26 |
# - stop_keystone |
| 27 | 27 |
# - cleanup_keystone |
| 28 |
-# - _cleanup_keystone_apache_wsgi |
|
| 29 | 28 |
|
| 30 | 29 |
# Save trace setting |
| 31 | 30 |
_XTRACE_KEYSTONE=$(set +o | grep xtrace) |
| ... | ... |
@@ -149,11 +148,7 @@ function is_keystone_enabled {
|
| 149 | 149 |
# cleanup_keystone() - Remove residual data files, anything left over from previous |
| 150 | 150 |
# runs that a clean run would need to clean up |
| 151 | 151 |
function cleanup_keystone {
|
| 152 |
- _cleanup_keystone_apache_wsgi |
|
| 153 |
-} |
|
| 154 |
- |
|
| 155 |
-# _cleanup_keystone_apache_wsgi() - Remove wsgi files, disable and remove apache vhost file |
|
| 156 |
-function _cleanup_keystone_apache_wsgi {
|
|
| 152 |
+ disable_apache_site keystone |
|
| 157 | 153 |
sudo rm -f $(apache_site_config_for keystone) |
| 158 | 154 |
} |
| 159 | 155 |
|