Skip to:
Steps to reproduce:
set as a destination folder with insufficient permissions (in our case local storage folder)
start backup with pbm backup --out=json
check status with pbm describe-backup <name>
Expected:
Both pbm status and pbm describe-backup reporting error status for the backup.
Actual:
pbm status reports error:
2023-04-28T09:42:33Z 0.00B <logical> [ERROR: Backup stuck at `starting` stage, last beat ts: 1682674954] [2023-04-28T09:42:34Z]
pbm describe-backup reports starting status:
name: "2023-04-28T09:42:33Z"opid: 644b9509a691c704d238b56dtype: logicallast_write_time: "1970-01-01T00:00:01Z"last_transition_time: "2023-04-28T09:42:34Z"mongodb_version: 5.0.8pbm_version: 2.0.5status: startingsize_h: 0 Breplsets: []
Backlog refinement notes: Proposed solution = improvement:
add stalelock detection after 30 seconds.
a note for devs: describe-backup should take into account stale heartbeats
Affected version 2.1.0
LowLowLow
Steps to reproduce:
set as a destination folder with insufficient permissions (in our case local storage folder)
start backup with pbm backup --out=json
check status with pbm describe-backup <name>
Expected:
Both pbm status and pbm describe-backup reporting error status for the backup.
Actual:
pbm status reports error:
2023-04-28T09:42:33Z 0.00B <logical> [ERROR: Backup stuck at `starting` stage, last beat ts: 1682674954] [2023-04-28T09:42:34Z]
pbm describe-backup reports starting status:
name: "2023-04-28T09:42:33Z"
opid: 644b9509a691c704d238b56d
type: logical
last_write_time: "1970-01-01T00:00:01Z"
last_transition_time: "2023-04-28T09:42:34Z"
mongodb_version: 5.0.8
pbm_version: 2.0.5
status: starting
size_h: 0 B
replsets: []