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-volume info throws KeyError: 'revisions_to_keep' #3900

Closed
bmup opened this Issue May 15, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@bmup

bmup commented May 15, 2018

Qubes OS version:

R4.0

Affected component(s):

qvm-volume info


Steps to reproduce the behavior:

1.) run qvm-ls from dom0
2.) select a VM from the NAME column, and run qvm-volume list
3.) now run qvm-volume info VMNAME:VOLUME_NAME for some row identified in step 2 above

Expected behavior:

information is listed about that volume

Actual behavior:

stack trace results:
qvm_volume.py line 307
sys.exit(main())
qvm_volume.py line 112
value = getattr(volume, item)
qvm_volume.py line 178
return int(self._info['revisions_to_keep'])
KeyError: 'revisions_to_keep'

General notes:

If I remove 'revisions_to_keep' from info_items list at line 95 of qvm_volume.py, then the command executes successfully (although revisions_to_keep information is of course not displayed.) I doubt that is the correct fix however, since at first glance it appears qvm_volume.py intends but fails to support this query. I have not tested qvm-volume info command on every VM/volume combination, but it fails in this same manner on every combination which I have tested.


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 15, 2018

Member

What version of qubes-core-dom0 package do you have? If older than 4.0.25, please update.

Member

marmarek commented May 15, 2018

What version of qubes-core-dom0 package do you have? If older than 4.0.25, please update.

@bmup

This comment has been minimized.

Show comment
Hide comment
@bmup

bmup May 15, 2018

Thank you, that resolves the problem.

bmup commented May 15, 2018

Thank you, that resolves the problem.

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