(mysql) incremental backup keeps instance in BACKUP state if backup has no lsn
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Triaged
|
High
|
Unassigned | ||
Bug Description
Related to this bug https:/
The incremental backup hangs for mysql if there is no lsn number because the status is never reported that the backup FAILED. The backup will stay in a BUILD state so this in turn keeps the instance also in the BACKUP state.
We need to make sure if there is an error in the guest for a backup that the guest reports it back to conductor/
Log of guest agent when incremental backup is created from a backup that has no lsn.
http://
To replicate:
Create a backup from an instance.
Delete the lsn number from the backup
make sure the backup is in COMPLETED state (a good state even though the backup is not)
create an incremental backup with the parent as the backup with no lsn
instance will never get out of BACKUP state.
| Changed in trove: | |
| milestone: | mitaka-1 → mitaka-3 |
| Changed in trove: | |
| milestone: | mitaka-3 → mitaka-rc1 |
| Changed in trove: | |
| milestone: | mitaka-rc1 → next |
