RFE: add configurable limit nova-status upgrade check for warning on archive/purge limit
Bug #1791824 reported by
Matt Riedemann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
This came up in the upgrades SIG room at the Stein PTG:
https:/
The request is that failing to archive/purge old deleted records from the database can cause upgrades to have major downtime because of the old records (heat and keystone are known major issues here, but clearly also instances records) - and they would like a nova-status upgrade check that checks some configured limit on deleted instances and warns if you should archive/purge prior to starting the upgrade.
The question would be what is a sane default (1000000 soft deleted instances records?), or something based on a time limit (deleted instances over 3 years old), etc.
Changed in nova: | |
importance: | Undecided → Wishlist |
tags: |
added: upgrade removed: upgrades |
To post a comment you must log in.
ML thread on this to socialize the request:
http:// lists.openstack .org/pipermail/ openstack- dev/2018- September/ 134532. html