This grenade bug was last updated over 180 days ago, as grenade is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it.
** Changed in: grenade Status: New => Invalid -- 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/1250525 Title: nova-conductor did not start after upgrade Status in grenade: Invalid Status in OpenStack Compute (nova): Invalid Bug description: From patch 4 in https://review.openstack.org/#/c/55251/ From http://logs.openstack.org/51/55251/4/check/check-grenade-devstack-vm/35a5476/console.html 2013-11-12 12:26:01.889 | The following services are not running after upgrade: nova-conductor This can be seen in the new n-cpu log: 2013-11-12 12:25:45.354 WARNING nova.conductor.api [req-ec7a159c-5dad- 4eda-9aa6-b98d6ba0d1f1 None None] Timed out waiting for nova- conductor. Is it running? Or did this service start before nova- conductor? To manage notifications about this bug go to: https://bugs.launchpad.net/grenade/+bug/1250525/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp