Bug 1843534
| Summary: | libvirt: Fix virConnectGetDomainCapabilities() call with empty cache [rhel-8.2.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | libvirt | Assignee: | Andrea Bolognani <abologna> |
| Status: | CLOSED ERRATA | QA Contact: | Luyao Huang <lhuang> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 8.2 | CC: | abologna, crobinso, dyuan, fdeutsch, jdenemar, jsuchane, knoel, lhuang, lijin, lmen, mtessun, toneata, virt-maint, xuzhang, yalzhang |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 8.2 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-6.0.0-17.3.el8 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: With version 6.0.0, libvirt started querying emulator capabilities lazily to improve startup time: this means that information about the default emulator for the host are only fetched if at least one of the defined VMs uses it.
Consequence: If no VMs using it are defined, virConnectGetDomainCapabilities() fails because information about the default emulator for the host are not found in the cache.
Fix: When virConnectGetDomainCapabilities() is called, information about the default emulator for the host are fetched unconditionally.
Result: virConnectGetDomainCapabilities() succeeds and reports information about the default emulator for the host.
|
Story Points: | --- |
| Clone Of: | 1836351 | Environment: | |
| Last Closed: | 2020-07-29 22:30:00 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: | 1836351 | ||
| Bug Blocks: | 1842869 | ||
|
Comment 6
yalzhang@redhat.com
2020-06-08 09:42:59 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. https://access.redhat.com/errata/RHBA-2020:3234 |