yahoo-eng-team team mailing list archive

[Eric Kessels <e.kessels@xxxxxxxxxxxx>]

Public bug reported:

Hi,

When you change the meta-data on a flavor this change is not migrated
into the nova table instance_extra. So when you change the flavor and
you cold migrate the instance, it still uses the old meta-data spec set
during initial creation.

The behaviour creates inconsistancy between flavor meta-data and
instance meta-data.

In my opinion it should work the same as when you change meta-data on a
volume type that when you migrate or live migrate the meta-data change
is reflected to the objects meta-date.

To reproduce:

1. Create flavor with meta-data quota:disk_read_iops_sec value '4455667788' (easy to trace in mysql)
2. Launch instance (ephemeral disk). 
3. The meta-data value is set in db=nova, table=instance_extra for the specific instance_uuid
4. Change meta-data quota:disk_read_iops_sec value '4455667788' to '4455667799' on the flavor
5. When you migrate, live-migrate or rebuild, the change does not reflect in the database and also not reflected in the XML on the Hypervisor
6. When you manual update the value in DB (UPDATE instance_extra SET flavor = REPLACE(flavor, '4455667788', '4455667799') WHERE INSTR(flavor, '4455667788') > 0;) when you do a live-migrate the change is not reflected on the xml on the hypervisor, when you migrate the change reflects the xml on the hypervisor

Version: queens
OS: Ubuntu 16.04

Eric

** Affects: nova
     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/1791048

Title:
  metadata change on flavor not migrated into DB after cold migrate

Status in OpenStack Compute (nova):
  New

Bug description:
  Hi,

  When you change the meta-data on a flavor this change is not migrated
  into the nova table instance_extra. So when you change the flavor and
  you cold migrate the instance, it still uses the old meta-data spec
  set during initial creation.

  The behaviour creates inconsistancy between flavor meta-data and
  instance meta-data.

  In my opinion it should work the same as when you change meta-data on
  a volume type that when you migrate or live migrate the meta-data
  change is reflected to the objects meta-date.

  To reproduce:

  1. Create flavor with meta-data quota:disk_read_iops_sec value '4455667788' (easy to trace in mysql)
  2. Launch instance (ephemeral disk). 
  3. The meta-data value is set in db=nova, table=instance_extra for the specific instance_uuid
  4. Change meta-data quota:disk_read_iops_sec value '4455667788' to '4455667799' on the flavor
  5. When you migrate, live-migrate or rebuild, the change does not reflect in the database and also not reflected in the XML on the Hypervisor
  6. When you manual update the value in DB (UPDATE instance_extra SET flavor = REPLACE(flavor, '4455667788', '4455667799') WHERE INSTR(flavor, '4455667788') > 0;) when you do a live-migrate the change is not reflected on the xml on the hypervisor, when you migrate the change reflects the xml on the hypervisor

  Version: queens
  OS: Ubuntu 16.04

  Eric

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