Description of problem:
A live merge failed due to "General Exception: ('volumeChain',)". More specifically, in the vdsm logs;
2018-06-19 19:14:21,666+0200 ERROR (jsonrpc/5) [api] FINISH merge error=volumeChain (api:132)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 122, in method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 736, in merge
drive, baseVolUUID, topVolUUID, bandwidth, jobUUID)
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5837, in merge
chains = self._driveGetActualVolumeChain([drive])
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5980, in _driveGetActualVolumeChain
volChain = drive.parse_volume_chain(diskXML)
File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 823, in parse_volume_chain
entry = VolumeChainEntry(self.volume_id(path), path, alloc, index)
File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 769, in volume_id
for vol in self.volumeChain:
AttributeError: volumeChain
The xml did not contain any "volumeChain" entries;
$ grep volumeChain vm-x_dumpxml
$
Version-Release number of selected component (if applicable):
RHV 4.2.3
redhat-release-virtualization-host-4.2-3.1.el7
vdsm-4.20.27.2-1.el7
libvirt-*-3.9.0-14.el7_5.5
qemu-kvm-rhev-2.10.0-21.el7_5.3
How reproducible:
Not.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 12Sandro Bonazzola
2019-01-28 09:44:36 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
It looks like the information received from Libvirt is missing the 'volumeChain' attribute for the disk.
Nir, Do we have anything to do with that missing information in that case?
(In reply to Eyal Shenitzky from comment #17)
> It looks like the information received from Libvirt is missing the
> 'volumeChain' attribute for the disk.
I'm not aware of any volumeChain attribute in libvirt response.
> Nir, Do we have anything to do with that missing information in that case?
If you think that this is a libvirt issue, please ask libvirt developer
to look at it.
Description of problem: A live merge failed due to "General Exception: ('volumeChain',)". More specifically, in the vdsm logs; 2018-06-19 19:14:21,666+0200 ERROR (jsonrpc/5) [api] FINISH merge error=volumeChain (api:132) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 122, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 736, in merge drive, baseVolUUID, topVolUUID, bandwidth, jobUUID) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5837, in merge chains = self._driveGetActualVolumeChain([drive]) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5980, in _driveGetActualVolumeChain volChain = drive.parse_volume_chain(diskXML) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 823, in parse_volume_chain entry = VolumeChainEntry(self.volume_id(path), path, alloc, index) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 769, in volume_id for vol in self.volumeChain: AttributeError: volumeChain The xml did not contain any "volumeChain" entries; $ grep volumeChain vm-x_dumpxml $ Version-Release number of selected component (if applicable): RHV 4.2.3 redhat-release-virtualization-host-4.2-3.1.el7 vdsm-4.20.27.2-1.el7 libvirt-*-3.9.0-14.el7_5.5 qemu-kvm-rhev-2.10.0-21.el7_5.3 How reproducible: Not. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: