New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-backup-restore: VM with rename gets restored, although excluded by not given in list of VMs to restore #2999

Closed
blackpit73 opened this Issue Aug 9, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@blackpit73

blackpit73 commented Aug 9, 2017

Qubes OS version (e.g., R3.2): R4.0-rc1

Actual behavior:

VM with rename gets restored, although excluded by not given in list of VMs to restore: If I give a list of VMs to restore, an VM gets restored, that is not on that list, because it is detected to be renamed.

Example:
qvm-backup-restore --rename-conflicting --passphrase-file test.passphrase qubes-2017-08-09T165253 backuptest-1-vm

-----------------+-------+-----------+-----------+--------+
name | type | template | netvm | label |
-----------------+-------+-----------+-----------+--------+
backuptest-2-vm | AppVM | fedora-25 | (default) | yellow | <-- Will be renamed to 'backuptest-2-vm1'
backuptest-1-vm | AppVM | fedora-25 | (default) | yellow | <-- Will be renamed to 'backuptest-1-vm1'

==> backuptest-2-vm will be restored as backuptest-2-vm1, although only backuptest-1-vm should be restored (at least from my expectation).

Steps to reproduce the behavior:

#-- test preparation
qvm-create -l yellow backuptest-1-vm
qvm-create -l yellow backuptest-2-vm
echo -n passphrase >test.passphrase

#-- create backup with backuptest-1-vm and backuptest-2-vm
qvm-backup --passphrase-file test.passphrase --yes pwd backuptest-1-vm backuptest-2-vm

#-- should only restore backuptest-1-vm, not backuptest-2-vm
qvm-backup-restore --rename-conflicting --passphrase-file test.passphrase qubes-2017-08-09T165253 backuptest-1-vm

@blackpit73

This comment has been minimized.

Show comment
Hide comment
@blackpit73

blackpit73 Aug 9, 2017

seems to be a duplicate of #2983

seems to be a duplicate of #2983

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment