volume backup service might not be available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
In Progress
|
Undecided
|
Pavlo Shchelokovskyy |
Bug Description
This is somewhat related to
- https:/
- https:/
The point is, cinder-backup service is optional, and there is currently no way to discover if it is available via Cinder API using only normal user-scoped token.
There is a spec https:/
- snapshot a stack that has a volume resource
- delete a stack that has a volume resource with deletion_policy set to Snapshot
What more, in a latter case, when cinder-backup service is absent it is perfectly possible to create such stack, but an attempt to delete it will result in undeletable stack even if the volume deleted manually.
Until discovery of cinder-backup service is implemented, I propose to add a config option to configure if it is is available and use it in validation of volume resources.
Alternatively, we could issue an admin-scoped cinderclient request during validation to check if cinder-backup service is available. Downside is yet another API call on validation.
Yet another alternative is to silently ignore the failure to backup the volume on deletion, but that would be really frustrating to users expecting the backup to be created (the funny thing is, even when cinder-backup is not running, backups.list() still returns possibly empty list of backups).
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
Fix proposed to branch: master /review. openstack. org/332851
Review: https:/