https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/5235/steps/18/logs/stdio AssertionError: Ping timeout error for address 192.168.7.2, count 0, output: PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable --- 192.168.7.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms We fixed the previous occurrences by fixing a systemd/connman issue. Is it related to the cancellation of this build?
We should get the kernel log from the qemu guest. For now we'll track it to see if it happens frequently.
Dunfell occurrence: https://autobuilder.yoctoproject.org/typhoon/#/builders/107/builds/3147 qemuppc-alt fedora35-ty-2
Dunfell occurrence on 3.1.20-rc2 build https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5934/steps/13/logs/stdio
Dunfell occurrence: https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/6514 qemuppc fedora36-ty-2
Dunfell specific and hasn't happened in 6 months.