Misspelled encryption field in QemuImgInfo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Zhongyue Luo | ||
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Peter Hamilton | ||
oslo-incubator |
Fix Released
|
Undecided
|
Peter Hamilton |
Bug Description
Location: openstack.
Method: __init__
Error: line 45, self.encryption = details.
The parsing of the encryption field for qemu-img commands does not work. The key used to index the details dictionary for encryption information, 'encryption', does not match the key generated by qemu-img, 'encrypted.' As a result, the encryption field is always 'None', regardless of the image's encryption status.
Example call to 'qemu-img info':
$ qemu-img info encrypted_
Disk image 'encrypted_
password:
image: encrypted_
file format: qcow2
virtual size: 16G (17179869184 bytes)
disk size: 136K
encrypted: yes
cluster_size: 65536
backing file: debian_
Proposed Fix:
Simply change the key used to index the encryption information.
self.encrypted = details.
Since the fields in __init__ seem to be named to match the keys used to index the corresponding information, I would also propose changing the attribute from self.encryption to self.encrypted, and updating any references to it wherever appropriate.
affects: | nova → cinder |
affects: | cinder → nova |
tags: | added: libvirt |
Changed in nova: | |
assignee: | nobody → Peter Hamilton (peter-hamilton) |
Changed in nova: | |
status: | New → In Progress |
Changed in cinder: | |
assignee: | nobody → ling-yun (zengyunling) |
Changed in cinder: | |
status: | New → In Progress |
Changed in oslo: | |
milestone: | none → icehouse-2 |
Changed in oslo: | |
status: | Fix Committed → Fix Released |
Changed in oslo: | |
milestone: | icehouse-2 → 2014.1 |
Changed in cinder: | |
status: | In Progress → Fix Released |
Changed in nova: | |
status: | In Progress → Fix Released |
For some reason (perhaps because this bug spans projects) the bug patch I've submitted for this has not been linked.
https:/ /review. openstack. org/#/c/ 60500/
I'm not sure what the process is for cross-project bug fixes, but once the nova patch is approved I plan on submitting the same for cinder. I tagged oslo in this bug report since the bug affects openstack.common, but I don't know if anything different needs to be done to account for an oslo bug fix.