yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Changed in: nova
   Importance: Undecided => Medium

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

** Changed in: nova/rocky
   Importance: Undecided => Medium

** Changed in: nova/rocky
       Status: New => Confirmed

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

Title:
  A new instance_mapping record will have queued_for_delete set to NULL

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) rocky series:
  Confirmed

Bug description:
  After this change: https://review.openstack.org/#/c/584504, where we
  changed the default value of queued_for_delete column from False to
  NULL in the sqla code for the instance_mappings object (to do the data
  migration for queued_for_delete), we forgot to set the default value
  as False upon creation of the new instance_mappings in the create()
  method. Hence new instance_mappings always ended up with NULL values
  in the db meaning the data migration "populate_queued_for_delete"
  would never finish.

  So in the InstanceMapping.create() function queued_for_delete should
  always be set to False() explicitly so that new mappings get False as
  the default value.

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