Bug 908274
Summary: | $dev->get_parent() can't get undef if there is no parent | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | zhe peng <zpeng> | |
Component: | perl-Sys-Virt | Assignee: | Daniel Berrangé <berrange> | |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 6.4 | CC: | cwei, dyuan, jherrman, jsuchane, mzhan, weizhan | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | perl-Sys-Virt-0.10.2-6.el6 | Doc Type: | Bug Fix | |
Doc Text: |
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.
|
Story Points: | --- | |
Clone Of: | ||||
: | 994141 (view as bug list) | Environment: | ||
Last Closed: | 2015-07-22 07:24:35 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: |
Description
zhe peng
2013-02-06 10:15:08 UTC
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> verify with build:perl-Sys-Virt-0.10.2-6.el6.x86_64 step: same step with bug description no libvirt error return. move to verified. 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 |