Description of problem:
There are some situations that the only way to recover from an overcloud stack update failure is to recover undercloud backups. The problem is that several operators don't keep up to date backups of undercloud.
The request is to include an undercloud configuration option that would automatically generate backups of database and perhaps critical configuration files after a successful stack create or update.
Example of situation in which this would help: someone mistakenly scales down compute nodes through a typo in a deployment script
I'm setting version to "OSP 13" because this is the current long life release.
By default, we should always keep at least one backup to conserve on space. The number of backups to keep should be configurable via the "undercloud.conf" configuration file.
Added PM for comment on this RFE for future prioritization.
Currently, there is no commitment to automate backup as a supported feature.
Operationally, this can be done outside without requiring official support.
Comment 15Red Hat Bugzilla
2023-09-15 01:28:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days