When restarting the c-bak service snapshot status is always backing-up
Bug #1938488 reported by
ZhaoYixin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
In Progress
|
Low
|
Unassigned | ||
Bug Description
When the volume is backed up by snapshot, restart the cinder-backup service at this time.
The snapshot status will not be rolled back to available, but will remain in backing-up.
| affects: | masakari-monitors → cinder |
| tags: | added: backup-service |
Revision history for this message
| Sofia Enriquez (lsofia-enriquez) wrote | #1 |
| Changed in cinder: | |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| tags: | added: snapshot |
| summary: |
- Snapshot status is always backing-up + When restarting the c-bak service snapshot status is always backing-up |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #2 |
| Changed in cinder: | |
| status: | Incomplete → In Progress |
To post a comment you must log in.
Greetings ZhaoYixin,
If I'm understanding correctly, restarting the c-bak service will make the snapshot stay at a backing-up state forever? This is interesting because as far as I know the backup service shouldn't impact snapshots.
Would you mind sharing more information in order to reproduce the issue easier?
- Steps to reproduce.
- Are you using a master or a stable version of cinder?
- What backend are you using? Currently, we have some issues regarding snapshots and generic NFS.
- Are you using encryption?
Cheers,
Sofia