yahoo-eng-team team mailing list archive

[Justin Shepherd <jshepher@xxxxxxxxxxxxx>]

Marking this issue as invalid, as it is filed against Essex, and has not
been updated in over a year and a half. If you believe this to be in
error, please update this issue.

** Changed in: nova
       Status: Confirmed => 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/1013726

Title:
  Essex upgrade doesn't ensure networks have uuid

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I've encountered problems on a 2012.1 cloud migrated from 2011.3 (*not
  2011.3.1*). After some investigation, I understood it was due to
  networks missing uuids (uuid field is NULL in networks table).

  From my understanding:
  This uuid field was added during the Diablo release cycle, with a migration generating uuids for existing networks. Fine.
  But : nova-manage network create was not setting uuids. This means that all networks created in 2011.3 (Diablo) have uuid=NULL. This was fixed in 2011.3.1.

  The situation now is: networks created in 2011.3 (2011.3 only, not
  2011.3.1) don't have uuids. On upgrade to 2012.1 (Essex), no migration
  ensures that uuids exist, and that is a source of problem. (In my case
  nova-compute was crashing when trying to launch instances which were
  not in the first network.)

  Doing a 2011.3->2011.3.1 update before moving to 2012.1 would probably
  not have changed anything in this case (the migration adding uuids was
  done when upgrading to 2011.3).

  Did I miss something? If not, I think it'd be worth fixing this in
  Essex.

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