Kilo grenade broken on disable_apache_site not found

Bug #1457631 reported by Sean McGinnis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

Grenade is failing on all backports to Kilo. At the end of the run it returns:

    /opt/stack/old/devstack/lib/keystone: line 569: disable_apache_site: command not found

The grenade log ends with:

2015-05-21 18:51:50.238 | + disable_apache_site keystone
2015-05-21 18:51:50.239 | /opt/stack/old/devstack/lib/keystone: line 569: disable_apache_site: command not found
2015-05-21 18:51:50.239 | + exit_trap
2015-05-21 18:51:50.239 | + local r=127
2015-05-21 18:51:50.239 | 1 stop_keystone /opt/stack/old/devstack/lib/keystone
2015-05-21 18:51:50.240 | + die 'Failed to shutdown keystone'
2015-05-21 18:51:50.240 | + local exitcode=1
2015-05-21 18:51:50.240 | [Call Trace]
2015-05-21 18:51:50.240 | ./grenade.sh:253:shutdown_services
2015-05-21 18:51:50.240 | /opt/stack/new/grenade/inc/plugin:58:die
2015-05-21 18:51:50.242 | [ERROR] /opt/stack/new/grenade/inc/plugin:Failed to
2015-05-21 18:51:51.245 | 1 die /opt/stack/new/devstack/functions-common

Revision history for this message
Jay Bryant (jsbryant) wrote :

Sean, I already opened a bug for this: https://bugs.launchpad.net/grenade/+bug/1456835

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.