yahoo-eng-team team mailing list archive

[Surya Seetharaman <1794994@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The nova-manage db archive_deleted_rows command from Queens started
archiving instance_mappings and request_specs records when moving the
soft_deleted instances records to the shadow tables. However since the
api tables do not have the concept of soft deletion, the
instance_mapping and request_spec tables are linked to instances table
while doing the archival. Hence the --max_rows parameter that is
specified does not count/include the count of instance_mapping and
request_spec rows that are removed. So the --verbose output of the
command may not look right when the number are really large.

We need to either update the documentation saying two more records per
instance record will be archived or stop showing the output of the
archived tables from the API db. I guess same applies for the recent
patch where we archive instance_group_members.

** Affects: nova
     Importance: Low
     Assignee: Surya Seetharaman (tssurya)
         Status: Confirmed


** Tags: cells nova-manage

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

** Changed in: nova
       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/1794994

Title:
  Update the --max-rows parameter description for nova-manage db
  archive_deleted_rows

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  The nova-manage db archive_deleted_rows command from Queens started
  archiving instance_mappings and request_specs records when moving the
  soft_deleted instances records to the shadow tables. However since the
  api tables do not have the concept of soft deletion, the
  instance_mapping and request_spec tables are linked to instances table
  while doing the archival. Hence the --max_rows parameter that is
  specified does not count/include the count of instance_mapping and
  request_spec rows that are removed. So the --verbose output of the
  command may not look right when the number are really large.

  We need to either update the documentation saying two more records per
  instance record will be archived or stop showing the output of the
  archived tables from the API db. I guess same applies for the recent
  patch where we archive instance_group_members.

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