Bug 2002675
| Summary: | [split daemon]Failed to execute virsh cmd without specified connect uri when using default setting | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | yafu <yafu> |
| Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
| libvirt sub component: | General | QA Contact: | yafu <yafu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | jsuchane, lizhu, lmen, mprivozn, smitterl, virt-maint, xuzhang |
| Version: | 9.0 | Keywords: | Regression |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-7.7.0-3.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 12:45:32 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: | 7.7.0 |
| Embargoed: | |||
I think this is fixed with the latest libvirt-7.7.0 build. Can you retest please? (In reply to Michal Privoznik from comment #1) > I think this is fixed with the latest libvirt-7.7.0 build. Can you retest > please? Yes, it is fixed with libvirt-7.7.0-3.el9.x86_64. Awesome, moving to ON_QA to satisfy the process. Verified with libvirt-7.8.0-1.el9.x86_64. Test steps: 1.Execute 'virsh list' without specified connect uri and not change the default libvirt.conf setting: #virsh list Id Name State -------------------------------- 1 avocado-vt-vm2 running 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 (new packages: libvirt), 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-2022:2390 |
Description of problem: [split daemon]Failed to execute virsh cmd without specified connect uri when using default setting Version-Release number of selected component (if applicable): libvirt-daemon-7.6.0-2.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Enable split daemon mode; 2.Check the virtqemud and virtproxyd/virtproxyd.socket daemon status: # systemctl status virtqemud ● virtqemud.service - Virtualization qemu daemon Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2021-09-09 09:20:45 EDT; 2s ago # systemctl status virtproxyd.socket ● virtproxyd.socket - Libvirt proxy local socket Loaded: loaded (/usr/lib/systemd/system/virtproxyd.socket; enabled; vendor preset: disabled) Active: active (listening) since Thu 2021-09-09 04:43:26 EDT; 4h 38min ago # systemctl status virtproxyd ○ virtproxyd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/virtproxyd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Thu 2021-09-09 09:19:45 EDT; 2min 4s ago 3.Execute virsh cmd: # virsh list error: failed to connect to the hypervisor error: no connection driver available for <null> Actual results: Failed to execute virsh cmd without specified connect uri when using default setting Expected results: Should execute virsh cmds without specified connect uri successfully when using default setting in /etc/libvirt/libvirt.conf. Additional info: