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 upUnable to restore backup from R3.1 to R3.1 & R3.2 #2168
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Chilinot
Jul 13, 2016
I forgot to add that this issue only happens if the "Ignore missing" is checked.
EDIT: I have added it to the description.
Chilinot
commented
Jul 13, 2016
•
|
I forgot to add that this issue only happens if the "Ignore missing" is checked. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Chilinot
Jul 13, 2016
Full output when run in terminal with debug mode:
[lucas@dom0 ~]$ qvm-backup-restore --ignore-missing --encrypted --debug /run/media/lucas/Lillextern/Backup/Laptop/Qubes/qubes-backup-2016-07-12T101504
Please enter the pass phrase that will be used to decrypt/verify the backup:
Checking backup content...
Working in temporary dir:/var/tmp/restore_K0mWC6
Extracting data: 1.0 MiB to restore
Run command[u'tar', u'-ixvf', '/run/media/lucas/Lillextern/Backup/Laptop/Qubes/qubes-backup-2016-07-12T101504', u'-C', u'/var/tmp/restore_K0mWC6', u'backup-header', u'backup-header.hmac', u'qubes.xml.000', u'qubes.xml.000.hmac']
Got backup header and hmac: backup-header, backup-header.hmac
Verifying file /var/tmp/restore_K0mWC6/backup-header
Loading hmac for file /var/tmp/restore_K0mWC6/backup-header
File verification OK -> Sending file /var/tmp/restore_K0mWC6/backup-header
Creating pipe in: /var/tmp/restore_K0mWC6/restore_pipe
Getting new file:qubes.xml.000
Getting hmac:qubes.xml.000.hmac
Verifying file /var/tmp/restore_K0mWC6/qubes.xml.000
Started sending thread
Moving to dir /var/tmp/restore_K0mWC6
Loading hmac for file /var/tmp/restore_K0mWC6/qubes.xml.000
File verification OK -> Sending file /var/tmp/restore_K0mWC6/qubes.xml.000
Getting new file:
Waiting for the extraction process to finish...Extracting file /var/tmp/restore_K0mWC6/qubes.xml.000
Running command [u'tar', u'-xkv', u'qubes.xml']
Removing file /var/tmp/restore_K0mWC6/qubes.xml.000
qubes.xml
Finished extracting thread
Extraction process finished with code:0
Loading file /var/tmp/restore_K0mWC6/qubes.xml
debian-8 is included in backup
whonix-ws is included in backup
whonix-gw is included in backup
fedora-23 is included in backup
anon-whonix is included in backup
vault is included in backup
personal is included in backup
web is included in backup
mail is included in backup
dev is included in backup
spotify is included in backup
encore is included in backup
Traceback (most recent call last):
File "/usr/bin/qvm-backup-restore", line 266, in <module>
main()
File "/usr/bin/qvm-backup-restore", line 151, in main
error_callback=error_callback)
File "/usr/lib64/python2.7/site-packages/qubes/backup.py", line 1906, in backup_restore_prepare
vms_to_restore = restore_info_verify(vms_to_restore, host_collection)
File "/usr/lib64/python2.7/site-packages/qubes/backup.py", line 1720, in restore_info_verify
vm_info['netvm'] = host_collection \
AttributeError: 'NoneType' object has no attribute 'name'
Chilinot
commented
Jul 13, 2016
|
Full output when run in terminal with debug mode:
|
andrewdavidwong
added
bug
C: core
P: major
labels
Jul 13, 2016
andrewdavidwong
added this to the Release 3.2 milestone
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2016
Member
What did you choose during installation in firstboot dialog? I guess "do nothing", right?
|
What did you choose during installation in firstboot dialog? I guess "do nothing", right? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2016
Member
It looks to be caused by missing default netvm. As a workaround create any netvm (may be not functional at all) and set as default one. Then after restore change default netvm to the restored one (as you probably want).
|
It looks to be caused by missing default netvm. As a workaround create any netvm (may be not functional at all) and set as default one. Then after restore change default netvm to the restored one (as you probably want). |
marmarek
self-assigned this
Jul 14, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Chilinot
Jul 14, 2016
@marmarek yes, precisely. When I performed the fresh install I selected "don't configure anything".
Chilinot
commented
Jul 14, 2016
|
@marmarek yes, precisely. When I performed the fresh install I selected "don't configure anything". |
marmarek
closed this
in
marmarek/old-qubes-core-admin@f15ddf7
Jul 18, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 19, 2016
Member
Automated announcement from builder-github
The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
|
Automated announcement from builder-github The package
|
marmarek
added
the
r3.2-dom0-cur-test
label
Jul 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 28, 2016
Member
Automated announcement from builder-github
The package qubes-core-dom0-3.2.7-1.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
marmarek
added
r3.2-dom0-stable
and removed
r3.2-dom0-cur-test
labels
Jul 28, 2016
added a commit
to QubesOS/qubes-core-admin
that referenced
this issue
Nov 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Nov 20, 2016
Member
Automated announcement from builder-github
The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
|
Automated announcement from builder-github The package
|
marmarek
added
the
r3.1-dom0-cur-test
label
Nov 20, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 4, 2016
Member
Automated announcement from builder-github
The package qubes-core-dom0-3.1.18-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Chilinot commentedJul 13, 2016
•
edited
Edited 1 time
-
Chilinot
edited Jul 13, 2016 (most recent)
Qubes OS version (e.g.,
R3.1):R3.1 & R3.2-rc
Affected TemplateVMs (e.g.,
fedora-23, if applicable):Unknown
Expected behavior:
List the names of the backup VM's in the backup file.
Actual behavior:
Popup window with error message:
Title: "Houston, we have a problem..."
Content:
Details:
Steps to reproduce the behavior:
The same happens when used in the terminal with the "--ignore-missing" option.
General notes:
When the restoration program attempts to list all VM's in the backup file so that I will be able to select which ones to restore it fails with the above error.
I created the backup in order to reinstall my system.
I selected all VM's except the firewall and net-vm.
The backup is encrypted.
First I installed R3.2-rc, failed with the same message.
Then I tried R3.1 since that was the stable release and the one I had installed previously.
Still failed with the above error.
Related issues:
#1124