RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 590058 [details]
unexpected exception (Error code:16) on vdsm-13

Description of problem:
I have VM in PAUSED status, click on "Run" button returns me "Unexpected exception (Error code:16)".
# vdsClient -s 0 list table
fdabf547-909a-4242-b957-be6d60bf1ca7  12617  win7-16-6-2          Paused 
# vdsClient -s 0 continue fdabf547-909a-4242-b957-be6d60bf1ca7
Unexpected exception

Version-Release number of selected component (if applicable):
# rpm -q vdsm libvirt qemu-kvm-rhev
vdsm-4.9.6-13.el6.x86_64
libvirt-0.9.10-21.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.294.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Traceback (most recent call last):
  File "/usr/share/vdsm/clientIF.py", line 275, in _recoverExistingVms
    vmObj.preparePaths(vmObj.getConfDevices()[vm.DISK_DEVICES])
  File "/usr/share/vdsm/vm.py", line 402, in getConfDevices
    self.normalizeDrivesIndices(devices[DISK_DEVICES])
  File "/usr/share/vdsm/vm.py", line 540, in normalizeDrivesIndices
    if not self._usedIndices.has_key(drv['iface']):
KeyError: 'iface'

Is this still reproducible?

(In reply to comment #2)
> Is this still reproducible?

Not yet. The env. is not available at the moment.

I think this patch http://gerrit.ovirt.org/#/c/6970/3 will fix this bug as well.

This bug is fixed by commit:

http://gerrit.ovirt.org/#/c/787/
Change-Id: I912cc1418e0df32d44bbc1a7c79c496aebd86c36