yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

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.

** Project changed: nova => grenade

** Also affects: devstack
   Importance: Undecided
       Status: New

** Changed in: devstack
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370763

Title:
  Not responding to grenade 'kill' command

Status in devstack - openstack dev environments:
  Confirmed
Status in Grenade - OpenStack upgrade testing:
  New

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...

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1370763/+subscriptions