yahoo-eng-team team mailing list archive

[Anthony Woods <awoods@xxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1182056 ***
    https://bugs.launchpad.net/bugs/1182056

** This bug has been marked a duplicate of bug 1182056
   Failed VM's not set to error state on exception

-- 
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/1178586

Title:
  scheduling failures leave baremetal instances stuck in BUILDING

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  This might not be baremetal specific - dunno.

  after ]
  /var/log/upstart/nova-scheduler.log:2013-05-10 09:10:10,911.911 14196 WARNING nova.scheduler.manager [req-1a8b0d73-253b-4999-aeca-00555a4d2e83 87b44714e906420a9e6a07f6835b5b61 c30643483cd849a6b61e98c6ccc03a66] Failed to schedule_run_instance: No valid host was found. Exceeded max scheduling attempts 3 for instance 6b566d0c-320d-4bed-bc7e-ad0ba725925d

  
  the following is shown in nova list:

  | 6b566d0c-320d-4bed-bc7e-ad0ba725925d | test-6b566d0c-320d-4bed-bc7e-
  ad0ba725925d | BUILD  | scheduling | NOSTATE

  full log: http://paste.ubuntu.com/5650528/

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