yahoo-eng-team team mailing list archive

[Jim Rollenhagen <jim@xxxxxxxxxxxxxxxxxx>]

I tend to think the instance should always be tagged with a "hypervisor"
for a record of where it was built. In the past this could cause
problems with the resource tracker, but those are long solved.

There's also the part of this where the logs are likely gone by now,
tripleo has changed its architecture up, etc. This is likely to be hard
to reproduce, even if we think it is a bug.

Going to close this as WONTFIX, feel free to reopen if you think I'm a
terrible person :)

** Changed in: nova
       Status: Confirmed => Won't Fix

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

Title:
  failed Ironic deploys can have incorrect hypervisor attribute in Nova

Status in Ironic:
  Invalid
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  I just booted 46 nodes at once from a single Ironic
  conductor/Nova/keystone etc all in one cloud.

  After this, according to Ironic:

   - 1 node was in maintenance mode (see bug 1326279) 5 have
  instance_uuid None and the rest are active.

  But according to Nova:

   - 8 are in ERROR spawning:
  (in nova) | eb0e1255-4da5-46cb-b8e4-d3e1059e1087 | hw-test-eb0e1255-4da5-46cb-b8e4-d3e1059e1087 | ERROR  | spawning   | NOSTATE     |                       |
  (in ironic) | ebd0e2c1-7630-4067-94c1-81771c1680b6 | eb0e1255-4da5-46cb-b8e4-d3e1059e1087 | power on    | active             | False       |
  (see bug 1341346)

   - 5 are in ERROR NOSTATE:
  (nova)| c389bb7b-1760-4e69-a4ea-0aea07ccd4d8 | hw-test-c389bb7b-1760-4e69-a4ea-0aea07ccd4d8 | ERROR  | -          | NOSTATE     | ctlplane=10.10.16.146 |
  nova show shows us that it has a hypervisor 
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | 8bc4357a-6b32-47de-b3ee-cec5b41e72d2       
  but in ironic there is no instance uuid (nor a deployment dict..):
  | 8bc4357a-6b32-47de-b3ee-cec5b41e72d2 | None                                 | power off   | None               | False       |

  This bug is about the Nova instance having a hypervisor attribute that
  is wrong :)

  I have logs for this copied inside the DC, but a) its a production
  environment, so only tripleo-cd-admins can look (due to me being
  concened about passwords being in the logs) and b) they are 2.6GB in
  size, so its not all that feasible to attach them to the bug anyhow
  :).

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