You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I happened to see a few coredumps after applying several of the ztp policies to an SNO VM cluster.
It seems to occur while the VM is rebooting to apply a machineconfig:
May 14 13:54:24 sno00001 systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:54:24 sno00001 systemd-coredump[69664]: Failed to send coredump datagram: Connection reset by peer
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
We can see this has occurred several times:
[root@sno00001 ~]# journalctl | grep coredump
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 13:44:41 sno00001 systemd-coredump[31133]: Failed to send coredump datagram: Connection reset by peer
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:54:24 sno00001 systemd-coredump[69664]: Failed to send coredump datagram: Connection reset by peer
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 14:00:17 sno00001 systemd-coredump[41551]: Failed to send coredump datagram: Connection reset by peer
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
A second instance of this occurred on another sno clusters as well:
May 14 15:45:05 sno00002 systemd[1]: crio-conmon-a83fc4e4e11dfaeb003c6a2a49d4543dae11e97864afbdf700ccac367f878e6b.scope: Succeeded.
May 14 15:45:05 sno00002 systemd[1]: crio-conmon-a83fc4e4e11dfaeb003c6a2a49d4543dae11e97864afbdf700ccac367f878e6b.scope: Consumed 62ms CPU time
May 14 15:45:05 sno00002 systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 15:45:05 sno00002 systemd-logind[1126]: Session 1 logged out. Waiting for processes to exit.
May 14 15:45:05 sno00002 systemd[1]: Stopping /run/user/1000 mount wrapper...
May 14 15:45:05 sno00002 systemd[1]: Stopped target Host and Network Name Lookups.
I happened to see a few coredumps after applying several of the ztp policies to an SNO VM cluster.
It seems to occur while the VM is rebooting to apply a machineconfig:
We can see this has occurred several times:
A second instance of this occurred on another sno clusters as well:
Only these policies had been applied:
The text was updated successfully, but these errors were encountered: