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.
Bug 1097969 - libvirt-python API baselineCPU doesn't generate exception
Summary: libvirt-python API baselineCPU doesn't generate exception
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: John Ferlan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1097968
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-15 01:55 UTC by Jincheng Miao
Modified: 2014-10-14 04:21 UTC (History)
6 users (show)

Fixed In Version: libvirt-0.10.2-37.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1097968
Environment:
Last Closed: 2014-10-14 04:21:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1374 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2014-10-14 08:11:54 UTC

Description Jincheng Miao 2014-05-15 01:55:48 UTC 
+++ This bug was initially created as a clone of Bug #1097968 +++

Description:
baselineCPU doesn't generate exception.

How reproducible:
100%

Version:
libvirt-python-1.1.1-29.el7.x86_64

Steps:
1.
# python
>>> import libvirt
>>> con=libvirt.open(None)
>>> con.baselineCPU([], 0)
libvirt:  error : xmlCPUs in virConnectBaselineCPU must not be NULL
-1
>>> ret = con.baselineCPU([], 0)
libvirt:  error : xmlCPUs in virConnectBaselineCPU must not be NULL
>>> print ret
-1

Expected results:
when the input is invalid, baselineCPU should generate an exception.
Comment 3 Xuesong Zhang 2014-05-26 09:24:08 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
Comment 5 errata-xmlrpc 2014-10-14 04:21:51 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.