yahoo-eng-team team mailing list archive

[OpenStack Infra <1786298@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/nova pike-eol  release.

** Changed in: nova/pike
       Status: Fix Committed => Fix Released

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

Title:
  nova-manage db archive_deleted_rows does not cleanup table
  instance_id_mappings

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Fix Committed
Status in OpenStack Compute (nova) rocky series:
  Fix Committed

Bug description:
  Description
  ===========
  After running nova-manage delete_archive_logs all tables are cleaned up except instance_id_mappings.

  Steps to reproduce
  ==================
  * create instance
  * delete instance
  * nova-manage delete_archive_logs

  Expected result
  ===============
  Clean up of instance_id_mappings table

  Actual result
  =============
  +-----------------------------+--------+---------+------------+--------+
  | Name                        | Engine | Version | Row_format | Rows   |
  +-----------------------------+--------+---------+------------+--------+
  | instance_id_mappings        | InnoDB |      10 | Compact    | 288549 |
  | shadow_instance_id_mappings | InnoDB |      10 | Compact    |      0 |
  +-----------------------------+--------+---------+------------+--------+

  Environment
  ===========
  openstack-nova-conductor-17.0.5-1.el7.noarch
  openstack-nova-scheduler-17.0.5-1.el7.noarch
  openstack-nova-api-17.0.5-1.el7.noarch
  openstack-nova-placement-api-17.0.5-1.el7.noarch
  openstack-nova-novncproxy-17.0.5-1.el7.noarch
  openstack-nova-console-17.0.5-1.el7.noarch
  openstack-nova-common-17.0.5-1.el7.noarch

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