Bug 836647
Summary: | OpenVZ driver returns fatal error with virConnectListDomains() when no domains available | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | David Shrewsbury <shrewsbury.dave> |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | berrange, crobinso, rbalakri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-23 21:39:43 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
David Shrewsbury
2012-06-29 19:10:48 UTC
Note: Although commit f0293edc3f2f147e04a837d47288253a9991677a will likely prevent this error for the Python API in v0.9.9, the OpenVZ driver should not be fatal for this call. David, I have a few suggestions. First, you should mention this BZ on the libvirt mailing list as I'm not sure how closely the openvz libvirt folks monitor bugzilla. Also, can you comment with whether this behavior reproduces with the upstream git HEAD? Finally, I don't run openvz myself, but it looks fairly straightforward to fix; would you consider submitting patches? -Dave Actually, this should be fixed with a newer version of vzctl: http://bugzilla.openvz.org/show_bug.cgi?id=2149 My test system (Ubuntu Precise) has vzctl 3.0.29.3. The problem is that vzctl (used directly by openvz/openvz_driver.c) will return non-zero on either error OR when no VMs are active. I'm not sure how we could (or even should) fix this for older versions of vzctl. Even though this is fixed, I'm inclined to think we should address this in libvirt, since the majority of historically deployed OpenVZ versions will have the flaw, and it is fairly painful for libvirt users. Never addressed in libvirt per comment #4, and this bug is old, so just closing. Patches welcome of course |