Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-backup-restore won't verify data when VMs already exist in system #3303
Comments
andrewdavidwong
added
bug
C: core
P: critical
labels
Nov 12, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Nov 12, 2017
tasket
referenced this issue
Dec 1, 2017
Closed
qvm-backup-restore verify-only: archives having dom0 yield NoneType error #3362
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
commented
Dec 1, 2017
|
Submitted PR QubesOS/qubes-core-admin-client#42 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Dec 1, 2017
Another bug inherent to this issue:
Spurious new VMs were created during the verify process. For example, if 'personal' VM didn't exist in the live system but you verified an archive containing a 'personal' VM then a new VM by that name would be created.
The submitted PR should prevent this also.
tasket
commented
Dec 1, 2017
|
Another bug inherent to this issue: Spurious new VMs were created during the verify process. For example, if 'personal' VM didn't exist in the live system but you verified an archive containing a 'personal' VM then a new VM by that name would be created. The submitted PR should prevent this also. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
commented
Jan 10, 2018
|
PR was merged. |
tasket
closed this
Jan 10, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Jan 11, 2018
Member
Keeping this open for builder-github (unless we know we don't need it tracked for some reason).
|
Keeping this open for |
andrewdavidwong
reopened this
Jan 11, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Never mind, looks like tracking works fine even if it's closed. |
tasket commentedNov 12, 2017
•
edited
Edited 1 time
-
tasket
edited Nov 12, 2017 (most recent)
Qubes OS version:
R4.0-rc2
Steps to reproduce the behavior:
qvm-backup-restore --verify-only -d backups /mnt/path-to-file
Expected behavior:
The backup file is read and verification results reported.
Actual behavior:
The following is shown almost instantly (thus no verification performed):
etc...
General notes:
This is with a fresh backup made in R4.
An additional error was shown at the very end:
Also, the messaging in 'app:' lines seems inappropriate given that
verify-onlyis used.Related issues: