Bug 1097969
Summary: | libvirt-python API baselineCPU doesn't generate exception | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jincheng Miao <jmiao> |
Component: | libvirt | Assignee: | John Ferlan <jferlan> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | dyuan, gsun, honzhang, mzhan, rbalakri, xuzhang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.10.2-37.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1097968 | Environment: | |
Last Closed: | 2014-10-14 04:21:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1097968 | ||
Bug Blocks: |
Description
Jincheng Miao
2014-05-15 01:55:48 UTC
Verify this bug with libvirt-0.10.2-37.el6.x86_64, get the exception while parse one invalid parameter to baselineCPU API. So, this bug is fixed, change the bug status to verified. steps: # python Python 2.6.6 (r266:84292, Nov 21 2013, 10:50:32) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import libvirt >>> con = libvirt.open('') >>> ret = con.baselineCPU([], 0) libvirt: error : xmlCPUs in virConnectBaselineCPU must not be NULL Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3393, in baselineCPU if ret is None: raise libvirtError ('virConnectBaselineCPU() failed', conn=self) libvirt.libvirtError: xmlCPUs in virConnectBaselineCPU must not be NULL >>> print ret Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'ret' is not defined Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1374.html |