This is a very nice and helpful tool, I had it working for mageia 9 on a package I created but a cockpit upgrade broke it, it complains of the webbrowser being to old but same happens with other web browsers. I've moved to Cauldron and it needs cockpit-ws269 wich is not working on cauldron byt now. Cockpit-machines lets you manage VMS and it is part of the cockpit project. https://github.com/cockpit-project/cockpit-machines
Created attachment 14882 [details] cockpit-machines.spec This is the cockpit-machines specs of the package I've created. Regards
Changing report to new package-request
Component: RPM Packages => New RPM package request
Severity: normal => enhancementCC: (none) => friAssignee: bugsquad => pkg-bugs
Mageia not support Boolean dependencies Suggests: (qemu-virtiofsd or virtiofsd) Should be for mageia 9 Recommends: qemu-virtiofsd And for cauldron Recommends: virtiofsd
(In reply to katnatek from comment #3) > Mageia not support Boolean dependencies > > Suggests: (qemu-virtiofsd or virtiofsd) > > Should be for mageia 9 > Recommends: qemu-virtiofsd > > And for cauldron > Recommends: virtiofsd understood. Thanks for letting me know katnatek.
Thanks for this suggestion. Before trying to import it in cauldron, I would like to ahve cockpit working. I have to update /etc/nsswitch.conf adding systemd. But now, I get an error with authentication, with the feel that Selinux is expected. I tried the cockpit.pam from openSuse, without success. Do you know how to do?
CC: (none) => yvesbrungard
(In reply to papoteur from comment #5) > Thanks for this suggestion. > Before trying to import it in cauldron, I would like to ahve cockpit working. > I have to update /etc/nsswitch.conf adding systemd. > But now, I get an error with authentication, with the feel that Selinux is > expected. > I tried the cockpit.pam from openSuse, without success. > Do you know how to do? I don't know about that topics, could you please post the full message?
CC: (none) => j.alberto.vc
Note for papoteur and myself, need to read https://cockpit-project.org/guide/latest/authentication
AS I understand the pam file https://github.com/cockpit-project/cockpit/blob/main/tools/cockpit.pam use selinux too @papoteur I don't know if you look something like this https://docs.redhat.com/es/documentation/red_hat_enterprise_linux_atomic_host/7/html-single/getting_started_with_cockpit/index#changing_expired_passwords
https://manpages.ubuntu.com/manpages/focal/man8/pam_cockpit_cert.8.html https://manpages.ubuntu.com/manpages/focal/man8/pam_ssh_add.8.html
I replaced /etc/pam.d/cockpit by /etc/pam.d/login, and now, I can authenticate. The build of cockpit-machines is OK, but the installation fails because of libwebkit2gtk and libvirt-dbus not provided
After removing the 2 failing dependencies, "Machines" application is available in cockpit. However, it displays just "Not found"
(In reply to papoteur from comment #11) > After removing the 2 failing dependencies, "Machines" application is > available in cockpit. However, it displays just "Not found" @Ezequiel can you bring some light on this, I don't use this software
I'll rework the spec based in latest from fedora
Created attachment 14979 [details] spec for cockpit-machines version 331 papoteur, I check the original spec and make some changes based on fedora's spec I integrate some changes suggested to Ezequiel
Attachment 14882 is obsolete: 0 => 1
Created attachment 14980 [details] spec for cockpit-machines version 331 Sorry I have to correct a line
Attachment 14979 is obsolete: 0 => 1
Created attachment 14987 [details] libvirt-dbus spec cockpit-machines require libvirt-dbus Here is the spec, I'll test if I can be built in cauldron
@papoteur libvirt-dbus is in cauldron do you require I make a Backport for mageia 9?
(In reply to katnatek from comment #17) > @papoteur libvirt-dbus is in cauldron do you require I make a Backport for > mageia 9? No if you don't plan to backport cockpit-machines
In cauldron now, please if you want a backport for mageia 9 open a new bug
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
@papoteur I make some fixes to Ezequiel original spec, let to your consideration if give credit in his process
(In reply to katnatek from comment #16) > Created attachment 14987 [details] > libvirt-dbus spec > > cockpit-machines require libvirt-dbus > Here is the spec, I'll test if I can be built in cauldron the libvirt-dbus service does not start. journalctl -e|grep libvirt juin 07 10:22:19 groupadd[3097]: group added to /etc/group: name=libvirtdbus, GID=970 juin 07 10:22:19 groupadd[3097]: group added to /etc/gshadow: name=libvirtdbus juin 07 10:22:19 groupadd[3097]: new group: name=libvirtdbus, GID=970 juin 07 10:22:19 useradd[3105]: new user: name=libvirtdbus, UID=979, GID=970, home=/, shell=/sbin/nologin, from=none juin 07 10:22:19 dbus-daemon[1466]: Unknown group "libvirt" in message bus configuration file juin 07 10:22:19 [RPM][3078]: install libvirt-dbus-1.4.1-1.mga10.x86_64: success juin 07 10:22:19 dbus-daemon[1466]: Unknown group "libvirt" in message bus configuration file juin 07 10:22:19 [RPM][3078]: install libvirt-utils-11.0.0-3.mga10.x86_64: success juin 07 10:22:20 [RPM][3078]: install libvirt-dbus-1.4.1-1.mga10.x86_64: success juin 07 10:22:20 [RPM][3078]: install libvirt-utils-11.0.0-3.mga10.x86_64: success juin 07 10:22:57 dbus-daemon[2357]: [session uid=1000 pid=2357] Activating via systemd: service name='org.libvirt' unit='libvirt-dbus.service' requested by ':1.48' (uid=1000 pid=22930 comm="/usr/bin/python3 /usr/bin/cockpit-bridge") juin 07 10:22:57 dbus-daemon[1466]: [system] Activating via systemd: service name='org.libvirt' unit='libvirt-dbus.service' requested by ':1.100' (uid=0 pid=22943 comm="/usr/bin/python3 /bin/cockpit-bridge --privileged") juin 07 10:22:57 systemd[2291]: Starting libvirt-dbus.service... juin 07 10:22:57 systemd[1]: Starting libvirt-dbus.service... juin 07 10:22:57 (irt-dbus)[23249]: libvirt-dbus.service: Failed to determine supplementary groups: No such process juin 07 10:22:57 systemd[1]: libvirt-dbus.service: Main process exited, code=exited, status=216/GROUP juin 07 10:22:57 systemd[1]: libvirt-dbus.service: Failed with result 'exit-code'. juin 07 10:22:57 systemd[1]: Failed to start libvirt-dbus.service. juin 07 10:22:57 dbus-daemon[2357]: [session uid=1000 pid=2357] Successfully activated service 'org.libvirt' juin 07 10:22:57 systemd[2291]: Started libvirt-dbus.service. juin 07 10:23:22 dbus-daemon[1466]: [system] Failed to activate service 'org.libvirt': timed out (service_start_timeout=25000ms) juin 07 10:23:55 urpmi[23453]: called with: libvirt-dbus
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
It seems that Fedora create a specific configuration file to use group libvirtdbus user https://src.fedoraproject.org/rpms/libvirt-dbus/blob/rawhide/f/libvirt-dbus.spec#_39
(In reply to papoteur from comment #22) > It seems that Fedora create a specific configuration file to use group > libvirtdbus user > https://src.fedoraproject.org/rpms/libvirt-dbus/blob/rawhide/f/libvirt-dbus. > spec#_39 Try libvirt-dbus-1.4.1-2.mga10 If I understand well it must be not working in fedora as is a configuration file "hardcoded" to use group libvirt
installing libvirt-dbus-1.4.1-3.mga10.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ################################################################################################### 1/1: libvirt-dbus ################################################################################################### 1/1: removing libvirt-dbus-1.4.1-2.mga10.x86_64 ################################################################################################### [root@localhost ~]# systemctl start libvirt-dbus.service [root@localhost ~]# systemctl status libvirt-dbus.service ● libvirt-dbus.service - Libvirt DBus Service Loaded: loaded (/usr/lib/systemd/system/libvirt-dbus.service; disabled; preset: disabled) Active: active (running) since Sun 2025-06-08 19:21:57 CST; 4s ago Main PID: 38850 (libvirt-dbus) Tasks: 5 (limit: 2311) Memory: 3.6M (peak: 4.1M) CPU: 41ms CGroup: /system.slice/libvirt-dbus.service └─38850 /usr/sbin/libvirt-dbus --system jun 08 19:21:57 localhost.localdomain systemd[1]: Starting libvirt-dbus.service... jun 08 19:21:57 localhost.localdomain systemd[1]: Started libvirt-dbus.service.
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED