[posix] cinder schedules incremental backups on the wrong node
Bug #1952805 reported by
Andrew Bogott
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I'm running 17.2 with the posix backend and two cinder-backup nodes.
When I run an incremental backup, the increment has a 50/50 chance of working: if it's scheduled on the same node that got the original full backup then it works, and if it gets scheduled on the other node with no full backup it fails:
2021-11-30 20:50:42.159 11905 ERROR oslo_messaging.
That file isn't found because it's on the other node, not this one.
summary: |
- cinder schedules incremental backups on the wrong node + [posix] cinder schedules incremental backups on the wrong node |
tags: | added: backup-service incremental posix schedules |
Changed in cinder: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/c/openstack /cinder/ +/861566
Review: https:/