Bug 2227980
| Summary: | virtnetworkd.service is not triggered by socket after first deactivation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | yalzhang <yalzhang> |
| Component: | libvirt | Assignee: | Virtualization Maintenance <virt-maint> |
| libvirt sub component: | Networking | QA Contact: | Virtualization Bugs <virt-bugs> |
| Status: | CLOSED DUPLICATE | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | chwen, lvivier, pkrempa, smitterl, virt-maint, yafu |
| Version: | 9.3 | Keywords: | Regression, TestOnly |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-01 07:00:14 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
yalzhang@redhat.com
2023-08-01 03:12:17 UTC
*** This bug has been marked as a duplicate of bug 2225667 *** observe similar situation in s390x platform, where virsh list is hanging
Steps follow as:
1) Execute automation case:/usr/local/bin/avocado --show=test,app run --test-runner=runner --vt-type libvirt --vt-machine-type s390-virtio --vt-connect-uri qemu:///system virsh.console.normal_test.non_acl.valid_domname
2)Find that case is hanging in :Starting vm 'avocado-vt-vm1'
3) Open another terminal ssh to s390x host, and execute : virsh list --all
4) Finding that: virsh list --all is hanging
5) After a few minutes, execute : virsh list --all again ,finding failed to connect to the hypervisor and virtqemud service crashed
[root@s390x-kvm-virtqez2 ~]# virsh list --all
error: failed to connect to the hypervisor
error: Operation not supported: Cannot use direct socket mode if no URI is set
[root@s390x-kvm-virtqez2 ~]# systemctl status virtqemud
× virtqemud.service - Virtualization qemu daemon
Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-08-04 05:23:29 EDT; 6min ago
Duration: 27min 1.868s
TriggeredBy: ○ virtqemud-ro.socket
○ virtqemud-admin.socket
○ virtqemud.socket
Docs: man:virtqemud(8)
https://libvirt.org
Main PID: 7638 (code=exited, status=1/FAILURE)
CPU: 577ms
observe similar situation in s390x platform, where virsh list is hanging
Steps follow as:
1) Execute automation case:/usr/local/bin/avocado --show=test,app run --test-runner=runner --vt-type libvirt --vt-machine-type s390-virtio --vt-connect-uri qemu:///system virsh.console.normal_test.non_acl.valid_domname
2)Find that case is hanging in :Starting vm 'avocado-vt-vm1'
3) Open another terminal ssh to s390x host, and execute : virsh list --all
4) Finding that: virsh list --all is hanging
5) After a few minutes, execute : virsh list --all again ,finding failed to connect to the hypervisor and virtqemud service crashed
[root@s390x-kvm-virtqez2 ~]# virsh list --all
error: failed to connect to the hypervisor
error: Operation not supported: Cannot use direct socket mode if no URI is set
[root@s390x-kvm-virtqez2 ~]# systemctl status virtqemud
× virtqemud.service - Virtualization qemu daemon
Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-08-04 05:23:29 EDT; 6min ago
Duration: 27min 1.868s
TriggeredBy: ○ virtqemud-ro.socket
○ virtqemud-admin.socket
○ virtqemud.socket
Docs: man:virtqemud(8)
https://libvirt.org
Main PID: 7638 (code=exited, status=1/FAILURE)
CPU: 577ms
|