Not responding to grenade 'kill' command

Bug #1370763 reported by Joshua Harlow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Undecided
Unassigned
grenade
Undecided
Unassigned

Bug Description

From a few recent gate failures it seems like nova-compute is not responding to being killed by grenade.

For example:

http://logs.openstack.org/66/121966/1/check/check-grenade-dsvm/c37f70d/logs/grenade.sh.txt.gz#_2014-09-17_00_16_47_262

The nova-compute process was requested to stop at 16_47,

It very much appears that nova-compute was idle at and before this time.

http://logs.openstack.org/66/121966/1/check/check-grenade-dsvm/c37f70d/logs/old/screen-n-cpu.txt.gz#_2014-09-17_00_16_28_611

Notice the last log there is from 16_28, nearly 20 seconds before shutdown was requested.

About 7 seconds (at 16_53) after being requested to stop via the command at 16_47 it appears like grenade still found nova-compute running.

http://logs.openstack.org/66/121966/1/check/check-grenade-dsvm/c37f70d/logs/grenade.sh.txt.gz#_2014-09-17_00_16_53_671

This then causes grenade to fail proceeding forward, and therefore stops the job from declaring success...

Revision history for this message
Sean Dague (sdague) wrote :

This isn't a nova issue, this is an issue with screen -X stuff sometimes dropping commands. There is work to change that in devstack / grenade.

affects: nova → grenade
Changed in devstack:
status: New → Confirmed
Revision history for this message
Dean Troyer (dtroyer) wrote :

The DevStack part of this was merged in https://review.openstack.org/#/c/117339/. The change to Grenade to not use screen has not been done yet.

Changed in grenade:
status: New → Confirmed
Changed in devstack:
status: Confirmed → Fix Committed
Sean Dague (sdague)
Changed in devstack:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers