yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

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

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

** Tags added: mitaka-backport-potential newton-backport-potential

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

Title:
  nova rebuild fails after two rebuild requests when ironic is used

Status in Ironic:
  Won't Fix
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) mitaka series:
  New
Status in OpenStack Compute (nova) newton series:
  New

Bug description:
  First nova rebuild request passes fine, but further requests fail with
  the following message:

  Instance b460e640-e601-4e68-b0e8-231e15201412 is already associated
  with a node, it cannot be associated with this other node
  10c0b922-cb39-412e-849a-27e66042d4c0 (HTTP 409)", "code": 500,
  "details": "  File \"/opt/stack/nova/nova/compute/manager.py\"

  The reason for this is that nova tries to reshcedule an instance
  during rebuild, and in case of ironic, there can't be 2 nodes
  associated with the same instance_uuid.

  This can be checked on devstack since change
  I0233f964d8f294f0ffd9edcb16b1aaf93486177f that introduced it with
  ironic virt driver and neutron.

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