[neon-notifications] Build failed in Jenkins: mgmt_digital-ocean #867

neon at kde.org neon at kde.org
Wed May 13 21:41:39 BST 2026 

See <https://build.neon.kde.org/job/mgmt_digital-ocean/867/display/redirect>

Changes:


------------------------------------------
[...truncated 89.24 KiB...]
Processing triggers for ufw (0.36.2-6) ...
Processing triggers for man-db (2.12.0-4build2) ...
Not building database; man-db/auto-update is not 'true'.
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for sgml-base (1.31) ...
Processing triggers for install-info (7.1-3build2) ...
Processing triggers for initramfs-tools (0.142ubuntu25.8) ...
update-initramfs: Generating /boot/initrd.img-6.8.0-101-generic
Processing triggers for linux-image-6.8.0-111-generic (6.8.0-111.111) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.8.0-111-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50-cloudimg-settings.cfg'
Sourcing file `/etc/default/grub.d/51-legacy-ifnames.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.0-111-generic
Found initrd image: /boot/initrd.img-6.8.0-111-generic
Found linux image: /boot/vmlinuz-6.8.0-101-generic
Found initrd image: /boot/initrd.img-6.8.0-101-generic
Found linux image: /boot/vmlinuz-6.8.0-100-generic
Found initrd image: /boot/initrd.img-6.8.0-100-generic
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Restarting services...
 systemctl restart fail2ban.service multipathd.service ssh.service udisks2.service

Service restarts being deferred:
 /etc/needrestart/restart.d/dbus.service
 systemctl restart getty at tty1.service
 systemctl restart serial-getty at ttyS0.service
 systemctl restart systemd-logind.service

No containers need to be restarted.

User sessions running outdated binaries:
 root @ session #4: apt[3228], bash[1562], sshd[1523]
 root @ user manager service: systemd[1389]

No VM guests are running outdated hypervisor (qemu) binaries on this host.
+ cd /tmp
+ wget https://omnitruck.chef.io/install.sh
--2026-05-13 20:41:31--  https://omnitruck.chef.io/install.sh
Resolving omnitruck.chef.io (omnitruck.chef.io)... 146.75.117.55
Connecting to omnitruck.chef.io (omnitruck.chef.io)|146.75.117.55|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 23738 (23K) [application/x-sh]
Saving to: ‘install.sh’

     0K .......... .......... ...                             100% 34.0M=0.001s

2026-05-13 20:41:31 (34.0 MB/s) - ‘install.sh’ saved [23738/23738]

+ chmod +x install.sh
+ ./install.sh -v 18
ubuntu 24.04 x86_64
Getting information for chef stable 18 for ubuntu...
downloading https://omnitruck.chef.io/stable/chef/metadata?v=18&p=ubuntu&pv=24.04&m=x86_64
  to file /tmp/install.sh.15011/metadata.txt
trying wget...
sha1	7c756fb02acf97d19327ee22c87c47516aab4f10
sha256	7e57c711d65fa7519df9c79ae4fa1af227a30533a877e078aed1f08b8a6fb120
url	https://packages.chef.io/files/stable/chef/18.10.17/ubuntu/24.04/chef_18.10.17-1_amd64.deb
version	18.10.17
downloaded metadata file looks valid...
downloading https://packages.chef.io/files/stable/chef/18.10.17/ubuntu/24.04/chef_18.10.17-1_amd64.deb
  to file /tmp/install.sh.15011/chef_18.10.17-1_amd64.deb
trying wget...
Comparing checksum with sha256sum...
Installing chef 18
installing with dpkg...
Selecting previously unselected package chef.
(Reading database ... 164583 files and directories currently installed.)
Preparing to unpack .../chef_18.10.17-1_amd64.deb ...
Unpacking chef (18.10.17-1) ...
Setting up chef (18.10.17-1) ...
Thank you for installing Chef Infra Client! For help getting started visit https://learn.chef.io
+ ./install.sh -v 23 -P chef-workstation
ubuntu 24.04 x86_64
Getting information for chef-workstation stable 23 for ubuntu...
downloading https://omnitruck.chef.io/stable/chef-workstation/metadata?v=23&p=ubuntu&pv=24.04&m=x86_64
  to file /tmp/install.sh.15107/metadata.txt
trying wget...
sha1	f5375ec22f4829ff03d9259fe7185f91ffc598e2
sha256	383b269ef486018b9d36849ba6267054085c296a097adf1bd00bd7446dee7452
url	https://packages.chef.io/files/stable/chef-workstation/23.12.1055/ubuntu/22.04/chef-workstation_23.12.1055-1_amd64.deb
version	23.12.1055
downloaded metadata file looks valid...
downloading https://packages.chef.io/files/stable/chef-workstation/23.12.1055/ubuntu/22.04/chef-workstation_23.12.1055-1_amd64.deb
  to file /tmp/install.sh.15107/chef-workstation_23.12.1055-1_amd64.deb
trying wget...
trying curl...
Comparing checksum with sha256sum...
Installing chef-workstation 23
installing with dpkg...
dpkg-deb: error: '/tmp/install.sh.15107/chef-workstation_23.12.1055-1_amd64.deb' is not a Debian format archive
dpkg: error processing archive /tmp/install.sh.15107/chef-workstation_23.12.1055-1_amd64.deb (--install):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 /tmp/install.sh.15107/chef-workstation_23.12.1055-1_amd64.deb
Installation failed
Version: 23

Please file a Bug Report at https://github.com/chef/omnitruck/issues/new
Alternatively, feel free to open a Support Ticket at https://www.chef.io/support/tickets
More Chef support resources can be found at https://www.chef.io/support

Please include as many details about the problem as possible i.e., how to reproduce
the problem (if possible), type of the Operating System and its version, etc.,
and any other relevant details that might help us with troubleshooting.

May 13 20:41:19 jenkins-slave-deploy systemd[1]: Reloading finished in 206 ms.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Stopping systemd-timesyncd.service - Network Time Synchronization...
May 13 20:41:19 jenkins-slave-deploy systemd[1]: systemd-timesyncd.service: Deactivated successfully.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Stopped systemd-timesyncd.service - Network Time Synchronization.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
May 13 20:41:19 jenkins-slave-deploy systemd-timesyncd[7890]: Contacted time server 185.125.190.58:123 (ntp.ubuntu.com).
May 13 20:41:19 jenkins-slave-deploy systemd-timesyncd[7890]: Initial clock synchronization to Wed 2026-05-13 20:41:19.158584 UTC.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Reloading requested from client PID 7902 ('systemctl') (unit session-4.scope)...
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Reloading...
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Reloading finished in 221 ms.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Stopping systemd-udevd.service - Rule-based Manager for Device Events and Files...
May 13 20:41:19 jenkins-slave-deploy systemd[1]: systemd-udevd.service: Deactivated successfully.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Stopped systemd-udevd.service - Rule-based Manager for Device Events and Files.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
May 13 20:41:19 jenkins-slave-deploy systemd-udevd[7947]: Using default interface naming scheme 'v255'.
May 13 20:41:19 jenkins-slave-deploy systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading requested from client PID 7955 ('systemctl') (unit session-4.scope)...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading finished in 203 ms.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: var-lib-machines.mount - Virtual Machine and Container Storage (Compatibility) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/machines.raw).
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading requested from client PID 8050 ('systemctl') (unit session-4.scope)...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading finished in 204 ms.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: fwupd-refresh.timer: Deactivated successfully.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Stopped fwupd-refresh.timer - Refresh fwupd metadata regularly.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Stopping fwupd-refresh.timer - Refresh fwupd metadata regularly...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Started fwupd-refresh.timer - Refresh fwupd metadata regularly.
May 13 20:41:20 jenkins-slave-deploy fwupd[7233]: 20:41:20.816 FuMain               Received SIGTERM
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Stopping fwupd.service - Firmware update daemon...
May 13 20:41:20 jenkins-slave-deploy systemd[1]: fwupd.service: Deactivated successfully.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Stopped fwupd.service - Firmware update daemon.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: fwupd.service: Consumed 1.932s CPU time, 189.1M memory peak, 0B memory swap peak.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Starting fwupd.service - Firmware update daemon...
May 13 20:41:20 jenkins-slave-deploy fwupd[8106]: 20:41:20.921 FuMain               fwupd 1.9.34 ready for requests (locale C.UTF-8)
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Started fwupd.service - Firmware update daemon.
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloading dbus.service - D-Bus System Message Bus...
May 13 20:41:20 jenkins-slave-deploy dbus-daemon[791]: [system] Reloaded configuration
May 13 20:41:20 jenkins-slave-deploy dbus-send[8114]: method return time=1778704880.952740 sender=org.freedesktop.DBus -> destination=:1.28 serial=3 reply_serial=2
May 13 20:41:20 jenkins-slave-deploy systemd[1]: Reloaded dbus.service - D-Bus System Message Bus.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading requested from client PID 8124 ('systemctl') (unit session-4.scope)...
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading...
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading finished in 204 ms.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Stopping systemd-resolved.service - Network Name Resolution...
May 13 20:41:21 jenkins-slave-deploy systemd[1]: systemd-resolved.service: Deactivated successfully.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
May 13 20:41:21 jenkins-slave-deploy systemd-resolved[8171]: Positive Trust Anchors:
May 13 20:41:21 jenkins-slave-deploy systemd-resolved[8171]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
May 13 20:41:21 jenkins-slave-deploy systemd-resolved[8171]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa corp home internal intranet lan local private test
May 13 20:41:21 jenkins-slave-deploy systemd-resolved[8171]: Using system hostname 'jenkins-slave-deploy'.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Started systemd-resolved.service - Network Name Resolution.
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading requested from client PID 8240 ('systemctl') (unit session-4.scope)...
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading...
May 13 20:41:21 jenkins-slave-deploy systemd[1]: Reloading finished in 209 ms.
May 13 20:41:22 jenkins-slave-deploy ModemManager[896]: <msg> caught signal, shutting down...
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Stopping ModemManager.service - Modem Manager...
May 13 20:41:22 jenkins-slave-deploy ModemManager[896]: <msg> ModemManager is shut down
May 13 20:41:22 jenkins-slave-deploy systemd[1]: ModemManager.service: Deactivated successfully.
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Stopped ModemManager.service - Modem Manager.
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Stopping polkit.service - Authorization Manager...
May 13 20:41:22 jenkins-slave-deploy systemd[1]: polkit.service: Deactivated successfully.
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Stopped polkit.service - Authorization Manager.
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Starting polkit.service - Authorization Manager...
May 13 20:41:22 jenkins-slave-deploy polkitd[8285]: Started polkitd version 124
May 13 20:41:22 jenkins-slave-deploy polkitd[8285]: Loading rules from directory /etc/polkit-1/rules.d
May 13 20:41:22 jenkins-slave-deploy polkitd[8285]: Loading rules from directory /usr/share/polkit-1/rules.d
May 13 20:41:22 jenkins-slave-deploy polkitd[8285]: Finished loading, compiling and executing 5 rules
May 13 20:41:22 jenkins-slave-deploy polkitd[8285]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Started polkit.service - Authorization Manager.
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Starting ModemManager.service - Modem Manager...
May 13 20:41:22 jenkins-slave-deploy ModemManager[8297]: <msg> ModemManager (version 1.23.4) starting in system bus...
May 13 20:41:22 jenkins-slave-deploy systemd[1]: Started ModemManager.service - Modem Manager.
May 13 20:41:22 jenkins-slave-deploy dbus-daemon[791]: [system] Reloaded configuration
May 13 20:41:26 jenkins-slave-deploy ModemManager[8297]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:03.0': not supported by any plugin
May 13 20:41:26 jenkins-slave-deploy ModemManager[8297]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:04.0': not supported by any plugin
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopping fail2ban.service - Fail2Ban Service...
May 13 20:41:30 jenkins-slave-deploy multipathd[342]: multipathd: shut down
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopping multipathd.service - Device-Mapper Multipath Device Controller...
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: Found left-over process 959 (sshd) in control group while starting unit. Ignoring.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: Found left-over process 960 (sshd) in control group while starting unit. Ignoring.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopping udisks2.service - Disk Manager...
May 13 20:41:30 jenkins-slave-deploy udisksd[804]: udisks daemon version 2.10.1 exiting
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: Found left-over process 959 (sshd) in control group while starting unit. Ignoring.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: Found left-over process 960 (sshd) in control group while starting unit. Ignoring.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: ssh.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: multipathd.service: Deactivated successfully.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopped multipathd.service - Device-Mapper Multipath Device Controller.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: udisks2.service: Deactivated successfully.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopped udisks2.service - Disk Manager.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Starting multipathd.service - Device-Mapper Multipath Device Controller...
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Starting udisks2.service - Disk Manager...
May 13 20:41:30 jenkins-slave-deploy sshd[14959]: Server listening on 0.0.0.0 port 22.
May 13 20:41:30 jenkins-slave-deploy sshd[14959]: Server listening on :: port 22.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
May 13 20:41:30 jenkins-slave-deploy udisksd[14963]: udisks daemon version 2.10.1 starting
May 13 20:41:30 jenkins-slave-deploy multipathd[14965]: multipathd v0.9.4: start up
May 13 20:41:30 jenkins-slave-deploy multipathd[14965]: reconfigure: setting up paths and maps
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Started multipathd.service - Device-Mapper Multipath Device Controller.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Started udisks2.service - Disk Manager.
May 13 20:41:30 jenkins-slave-deploy udisksd[14963]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May 13 20:41:30 jenkins-slave-deploy fail2ban-client[14956]: Shutdown successful
May 13 20:41:30 jenkins-slave-deploy systemd[1]: fail2ban.service: Deactivated successfully.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Stopped fail2ban.service - Fail2Ban Service.
May 13 20:41:30 jenkins-slave-deploy systemd[1]: Started fail2ban.service - Fail2Ban Service.
May 13 20:41:31 jenkins-slave-deploy fail2ban-server[14990]: 2026-05-13 20:41:31,096 fail2ban.configreader   [14990]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
May 13 20:41:31 jenkins-slave-deploy fail2ban-server[14990]: Server ready
May 13 20:41:37 jenkins-slave-deploy sshd[1523]: Close session: user root from 138.201.132.177 port 47182 id 0
May 13 20:41:37 jenkins-slave-deploy sshd[1523]: Received disconnect from 138.201.132.177 port 47182:11: disconnected by user
May 13 20:41:37 jenkins-slave-deploy sshd[1523]: Disconnected from user root 138.201.132.177 port 47182
May 13 20:41:37 jenkins-slave-deploy sshd[1523]: pam_unix(sshd:session): session closed for user root
May 13 20:41:37 jenkins-slave-deploy systemd[1]: session-4.scope: Deactivated successfully.
May 13 20:41:37 jenkins-slave-deploy systemd[1]: session-4.scope: Consumed 1min 6.403s CPU time, 1.4G memory peak, 0B memory swap peak.
May 13 20:41:37 jenkins-slave-deploy systemd-logind[802]: Session 4 logged out. Waiting for processes to exit.
May 13 20:41:37 jenkins-slave-deploy systemd-logind[802]: Removed session 4.
May 13 20:41:37 jenkins-slave-deploy sshd[15161]: Connection from 138.201.132.177 port 42524 on 164.90.185.184 port 22 rdomain ""
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: Accepted key RSA SHA256:sOyUAcvHDZukgIZzOZ/8toWMpzWnDOX8MIIQBtouP9E found at /root/.ssh/authorized_keys:3
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: Postponed publickey for root from 138.201.132.177 port 42524 ssh2 [preauth]
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: Accepted key RSA SHA256:sOyUAcvHDZukgIZzOZ/8toWMpzWnDOX8MIIQBtouP9E found at /root/.ssh/authorized_keys:3
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: Accepted publickey for root from 138.201.132.177 port 42524 ssh2: RSA SHA256:sOyUAcvHDZukgIZzOZ/8toWMpzWnDOX8MIIQBtouP9E
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
May 13 20:41:38 jenkins-slave-deploy systemd-logind[802]: New session 5 of user root.
May 13 20:41:38 jenkins-slave-deploy systemd[1]: Started session-5.scope - Session 5 of User root.
May 13 20:41:38 jenkins-slave-deploy sshd[15161]: Starting session: command for root from 138.201.132.177 port 42524 id 0
W, [2026-05-13T20:41:38.262329 #1015579]  WARN -- : deleting droplet
:delete
[]
{:id=>570798980}
/home/neonjenkins2/tooling/mgmt/digital_ocean.rb:103:in `<main>': unhandled exception
Build step 'Execute shell' marked build as failure

More information about the neon-notifications mailing list