Not responding to grenade 'kill' command
Bug #1370763 reported by
Joshua Harlow
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Unassigned | ||
grenade |
Confirmed
|
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:
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.
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.
This then causes grenade to fail proceeding forward, and therefore stops the job from declaring success...
Changed in devstack: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.