Snapshot Backup fails with remotefs based Drivers
Bug #1703405 reported by
Silvan Kaiser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
In Progress
|
Undecided
|
Silvan Kaiser | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The new tempest test for snapshot backups [1] fails with:
InvalidSnapshot: Snapshot status must be "available" to clone. But is: backing-up
Example log for the Quobyte driver at [2].
As the volume is in the 'backing-up' state the snapshot operation fails as it requires the volume to be in the state 'available'.
This probably hits every Driver that uses the default implementation of _create_
[1] https:/
[2] http://
tags: | added: quobyte |
Changed in tempest: | |
assignee: | nobody → Vishakha Agarwal (vishakha.agarwal) |
Changed in tempest: | |
assignee: | Vishakha Agarwal (vishakha.agarwal) → nobody |
To post a comment you must log in.
The tempest test only checks for "volume_ feature_ enabled. backup" , meaning it equates backup support with snapshot backup support. This is not correct, not all Cinder drivers support snapshot backup.