yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/stein
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

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

Title:
  MaxRetriesExceeded sometime fails with messaging exception

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  New
Status in OpenStack Compute (nova) rocky series:
  New
Status in OpenStack Compute (nova) stein series:
  New

Bug description:
  We are occasionally seeing MaxRetriesExceeded causing an "Exception
  during message handling" error. This prevents the database from
  setting the instance into error'd state and causes it to get stuck
  scheduling.

  Example logs:
  WARNING nova.scheduler.client.report [req-] Unable to submit allocation for instance x (409 {"errors": [{"status": 409, "request_id": "req-", "code": "placement.undefined_code", "detail": "There was a conflict when trying to complete your request.\n\n Unable to allocate inventory: Unable to create allocation for 'DISK_GB' on resource provider 'req-'. The requested amount would exceed the capacity.  ", "title": "Conflict"}]})
  ERROR oslo_messaging.rpc.server [req-] Exception during message handling: MaxRetriesExceeded: Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance x.

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