What were you trying to do that didn't work?

sudo dnf upgrade

What is the impact of this issue to you?

cockpit is no longer working

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

it happened once but it was enough

Steps to reproduce

1. sudo dnf upgrade

Expected results

all good

Actual results

some packages failed. after setenforce 0, packages instlled but services failed to start. again, with seteenfoce 0 most of them start, cut cockpit do not.
Upgrade error before relaxing selinux: (only one fragment)
Running transaction
Preparing : 1/1
Upgrading : podman-7:5.6.0-2.el10.x86_64 1/14
error: lsetfilecon: (29 /usr/bin/podman;68c92b92, system_u:object_r:container_runtime_exec_t:s0) Invalid argument
error: Plugin selinux: hook fsm_file_prepare failed

Failed services before relaxing selinux:
● pmcd.service loaded failed failed Performance Metrics Collector Daemon
● pmie_check.service loaded failed failed Check PMIE instances are running
● pmie_farm.service loaded failed failed pmie farm service
● pmie_farm_check.service loaded failed failed Check and migrate non-primary pmie farm instances
● pmlogger_check.service loaded failed failed Check pmlogger instances are running
● pmlogger_farm.service loaded failed failed pmlogger farm service
● pmlogger_farm_check.service loaded failed failed Check and migrate non-primary pmlogger farm instances
● cockpit-wsinstance-http.socket loaded failed failed Socket for Cockpit Web Service http instance
● cockpit.socket loaded failed failed Cockpit Web Service Socket

cockpit.socket status:

$ systemctl status cockpit.socket
× cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: enabled)
Active: failed (Result: trigger-limit-hit) since Tue 2025-09-16 12:41:04 EEST; 1min 36s ago
Duration: 1min 5.424s
Invocation: db6fa6cde2ed4b6694e6575e94e5e637
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 957 ExecStartPost=/usr/share/cockpit/issue/update-issue localhost (code=exited, status=1/FAILURE)
Process: 981 ExecStartPost=/bin/ln -snf active.issue /run/cockpit/issue (code=exited, status=1/FAILURE)
Process: 2930 ExecStopPost=/bin/ln -snf inactive.issue /run/cockpit/issue (code=exited, status=1/FAILURE)
Mem peak: 2.5M
CPU: 48ms
Sep 16 12:39:58 localhost systemd[1]: Starting cockpit.socket - Cockpit Web Service Socket...
Sep 16 12:39:59 localhost update-issue[957]: /usr/share/cockpit/issue/update-issue: line 24: /run/cockpit/active.issue: No such file or directory
Sep 16 12:39:59 localhost ln[981]: /bin/ln: failed to create symbolic link '/run/cockpit/issue': No such file or directory
Sep 16 12:39:59 localhost systemd[1]: Listening on cockpit.socket - Cockpit Web Service Socket.
Sep 16 12:41:04 localhost.localdomain systemd[1]: cockpit.socket: Trigger limit hit, refusing further activation.
Sep 16 12:41:04 localhost.localdomain ln[2930]: /bin/ln: failed to create symbolic link '/run/cockpit/issue': No such file or directory
Sep 16 12:41:04 localhost.localdomain systemd[1]: cockpit.socket: Failed with result 'trigger-limit-hit'.

/.autorelabel did not help (completd very fast, maybe it was not executed?)