Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Prior to this update, using the libvirt-tck utility to find the parent device of a node device with no parent incorrectly returned a "libvirt error code: 0" error message. Now, it is valid for the virNodeDeviceGetParent() function to return NULL if the parent device is nonexistent, and the error message is no longer displayed.
Description of problem:
When try to get parent of nodedev if there is no parent,libvirt-tck get error.
Version-Release number of selected component (if applicable):
libvirt-0.10.2-17.el6.x86_64
perl-Sys-Virt-0.10.2-5.el6.x86_64
kernel-2.6.32-348.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.in libvirt-tck script,added
.....
my @nodelist = $conn->list_all_node_devices();
foreach my $dev (@nodelist){
my $parent = $dev->get_parent();
diag $parent;
}
.....
Actual results:
libvirt error code: 0, message: Unknown problem
Expected results:
should return "undef"
Additional info:
the first item in nodelist is "computer",no parent.
use python interface can return "None".
commit 04470fa5412cbd04386c5c2e785e4672cc6e0e0f
Author: Daniel P. Berrange <berrange>
Date: Tue Aug 6 14:23:55 2013 +0100
Fix error handling for virNodeDeviceGetParent()
It is valid for virNodeDeviceGetParent() to return NULL in the
case where there is no parent device present.
Signed-off-by: Daniel P. Berrange <berrange>
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.
https://rhn.redhat.com/errata/RHBA-2015-1387.html
Description of problem: When try to get parent of nodedev if there is no parent,libvirt-tck get error. Version-Release number of selected component (if applicable): libvirt-0.10.2-17.el6.x86_64 perl-Sys-Virt-0.10.2-5.el6.x86_64 kernel-2.6.32-348.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.in libvirt-tck script,added ..... my @nodelist = $conn->list_all_node_devices(); foreach my $dev (@nodelist){ my $parent = $dev->get_parent(); diag $parent; } ..... Actual results: libvirt error code: 0, message: Unknown problem Expected results: should return "undef" Additional info: the first item in nodelist is "computer",no parent. use python interface can return "None".