yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

This change https://review.openstack.org/#/c/515034/ (added in queens)
makes the archive_deleted_rows CLI remove instance mappings and request
specs from the API database if there are instances archived from the
main nova/cell database.

However, with 'superconductor' mode configurations where the cell
shouldn't be configured to reach the API database, this will fail, as
seen here:

http://logs.openstack.org/71/550171/4/check/nova-next/4986796/logs
/devstack-gate-post_test_hook.txt.gz#_2018-03-06_20_44_21_017

So in the case that the API database isn't configured in the nova.conf
being used to run the CLI, we should gracefully handle the condition and
continue archiving.

I think we could either do this by handling the CantStartEngineError
from oslo.db or just check to see if CONF.api_database.connection is set
before attempting to hit records in the API DB.

** Affects: nova
     Importance: Medium
     Assignee: Surya Seetharaman (tssurya)
         Status: Triaged

** Affects: nova/queens
     Importance: Medium
         Status: Triaged


** Tags: db nova-manage

** Changed in: nova
       Status: New => Triaged

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

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

** Changed in: nova/queens
       Status: New => Triaged

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

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

Title:
  archive_deleted_rows --until-complete stops if api database is not
  configured

Status in OpenStack Compute (nova):
  Triaged
Status in OpenStack Compute (nova) queens series:
  Triaged

Bug description:
  This change https://review.openstack.org/#/c/515034/ (added in queens)
  makes the archive_deleted_rows CLI remove instance mappings and
  request specs from the API database if there are instances archived
  from the main nova/cell database.

  However, with 'superconductor' mode configurations where the cell
  shouldn't be configured to reach the API database, this will fail, as
  seen here:

  http://logs.openstack.org/71/550171/4/check/nova-next/4986796/logs
  /devstack-gate-post_test_hook.txt.gz#_2018-03-06_20_44_21_017

  So in the case that the API database isn't configured in the nova.conf
  being used to run the CLI, we should gracefully handle the condition
  and continue archiving.

  I think we could either do this by handling the CantStartEngineError
  from oslo.db or just check to see if CONF.api_database.connection is
  set before attempting to hit records in the API DB.

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