|
Bugzilla – Full Text Bug Listing |
| Summary: | Multiple broken parts of cockpit-ws and cockpit-machines | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Kai-ilja Görg <kaiilja> |
| Component: | Virtualization:Other | Assignee: | Adam Majer <amajer> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aginies, jfehlig, kevin.089 |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | cockpit-machines | ||
Same Problem here with the latest version of Tumbleweed. When I open machines in cockpit I get the message "Failed to fetch some resources. this function is not supported by the connection driver: virConnectListAllInterfaces". While logging into cockpit-ws to cockpit-machines from journal: Jul 05 11:34:37 bee systemd[1]: Started Libvirt DBus Service. Jul 05 11:34:37 bee libvirtd[5261]: this function is not supported by the connection driver: virConnectListAllInterfaces Jul 05 11:34:37 bee virtqemud[28119]: libvirt version: 9.4.0 Jul 05 11:34:37 bee virtqemud[28119]: hostname: bee Jul 05 11:34:37 bee virtqemud[28119]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied Jul 05 11:34:37 bee virtqemud[28119]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied Jul 05 11:34:37 bee virtqemud[28119]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied Jul 05 11:34:37 bee virtqemud[28119]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied Jul 05 11:34:37 bee virtnetworkd[28150]: libvirt version: 9.4.0 Jul 05 11:34:37 bee virtnetworkd[28150]: hostname: bee Jul 05 11:34:37 bee virtnetworkd[28150]: Unable to find 'dnsmasq' binary in $PATH: No such file or directory Jul 05 11:34:38 bee virtinterfaced[28295]: libvirt version: 9.4.0 Jul 05 11:34:38 bee virtinterfaced[28295]: hostname: bee Jul 05 11:34:38 bee virtinterfaced[28295]: Failed to initialize libnetcontrol. Management of interface devices is disabled I wonder if cockpit-machines assumes a monolithic libvirtd. Can it work with libvirt modular daemons, which is now the preferred setup in TW? For more info on libvirt daemon architecture see https://libvirt.org/daemons.html https://doc.opensuse.org/documentation/leap/virtualization/html/book-virtualization/cha-libvirt-overview.html (In reply to Kev from comment #1) > Same Problem here with the latest version of Tumbleweed. When I open > machines in cockpit I get the message "Failed to fetch some resources. this > function is not supported by the connection driver: > virConnectListAllInterfaces". This error (In reply to Kai-ilja Görg from comment #2) > While logging into cockpit-ws to cockpit-machines from journal: > > Jul 05 11:34:37 bee systemd[1]: Started Libvirt DBus Service. > Jul 05 11:34:37 bee libvirtd[5261]: this function is not supported by the > connection driver: virConnectListAllInterfaces This error is from the monolithic libvirtd. I'd also expect it to complain about inability to initialize libnetcontrol. libvirt uses libnetcontrol to manage host interface devices (ethX, brX, bondX, vlanX, etc), but libnetcontrol only works with wicked networking. If the host uses NetworkManager, libvirt cannot manage such host interface devices. What I find more troubling with this error is that it comes from the monolithic daemon when the next messages come from the modular daemons. The monolithic and modular daemons should not be used concurrently. In fact, the virtqemud.service unit conflicts with libvirtd.service, so libvirtd should be shutdown when virtqemud activates. > Jul 05 11:34:37 bee virtqemud[28119]: libvirt version: 9.4.0 > Jul 05 11:34:37 bee virtqemud[28119]: hostname: bee > Jul 05 11:34:37 bee virtqemud[28119]: Failed to open file > '/sys/kernel/security/apparmor/profiles': Permission denied > Jul 05 11:34:37 bee virtqemud[28119]: Failed to read AppArmor profiles list > '/sys/kernel/security/apparmor/profiles': Permission denied > Jul 05 11:34:37 bee virtqemud[28119]: Failed to open file > '/sys/kernel/security/apparmor/profiles': Permission denied > Jul 05 11:34:37 bee virtqemud[28119]: Failed to read AppArmor profiles list > '/sys/kernel/security/apparmor/profiles': Permission denied > Jul 05 11:34:37 bee virtnetworkd[28150]: libvirt version: 9.4.0 > Jul 05 11:34:37 bee virtnetworkd[28150]: hostname: bee > Jul 05 11:34:37 bee virtnetworkd[28150]: Unable to find 'dnsmasq' binary in > $PATH: No such file or directory That's odd. Is dnsmasq installed in an "unusual" location? I assume it's installed since the libvirt-daemon-driver-network package requires dnsmasq. > Jul 05 11:34:38 bee virtinterfaced[28295]: libvirt version: 9.4.0 > Jul 05 11:34:38 bee virtinterfaced[28295]: hostname: bee > Jul 05 11:34:38 bee virtinterfaced[28295]: Failed to initialize > libnetcontrol. Management of interface devices is disabled This is the message I'd also expect to see from the monolithic daemon telling that libnetcontrol+wicked could not be initialized. Fixed in cockpit-machines 295! Looks great now, Big up`s and many thanks to the maintainers. PS: @James Fehlig I have to study libvirt daemon architecture a bit more, thank you for pointing to the docs. Wicked is up in the queue ;) |
Created attachment 867986 [details] cockpit-machines In the latest version the combination of podman cockpit-ws container, on top of openSUSE Tumbleweed, the webinterface items are de-arranged, so for instance the network tab in cockpit-machines is unusable. Despite that there are multiple not functional value fields, like Memory, Naming etc. This is since I upgraded the cockpit plugins, I testet various container versions and vendors. Same. Can someone reproduce this behaviour?