yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

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

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

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

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

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

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

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

** Tags added: db upgrades

** Changed in: nova/ocata
   Importance: Undecided => High

** Changed in: nova/mitaka
   Importance: Undecided => High

** Changed in: nova/newton
   Importance: Undecided => High

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

Title:
  PCI device migration cannot continue with old deleted service records

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) mitaka series:
  Confirmed
Status in OpenStack Compute (nova) newton series:
  Confirmed
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  If deleted service records are present in the database, the Service
  minimum version calculation should ignore them, but it does not. One
  manifestation of this is the PCI device migration from mitaka/newton
  will never complete, emitting an error message like this:

  2017-02-27 07:40:19.665 ERROR nova.db.sqlalchemy.api [req-ad21480f-
  613a-445b-a913-c54532b64ffa None None] Data migrations for PciDevice
  are not safe, likely because not all services that access the DB
  directly are updated to the latest version

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