Bug 14824

Summary:	AB-INT: ping.PingTest.test_ping failure
Product:	[QA/Testing] Functional (self) Testing	Reporter:	Alexandre Belloni <alexandre.belloni>
Component:	oe-selftest	Assignee:	Unassigned <unassigned>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Medium	CC:	alexandre.belloni, randy.macleod, steve
Version:	unspecified
Target Milestone:	4.3
Hardware:	x86
OS:	Multiple
Whiteboard:	AB-INT AB-INT-NET
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Alexandre Belloni 2022-06-02 16:36:56 UTC

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?

Comment 1 Randy MacLeod 2022-06-09 14:34:57 UTC

We should get the kernel log from the qemu guest.
For now we'll track it to see if it happens frequently.

Comment 2 Steve Sakoman 2022-06-16 17:09:05 UTC

Dunfell occurrence:

https://autobuilder.yoctoproject.org/typhoon/#/builders/107/builds/3147

qemuppc-alt fedora35-ty-2

Comment 3 Steve Sakoman 2022-10-10 17:13:55 UTC

Dunfell occurrence on 3.1.20-rc2 build

https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5934/steps/13/logs/stdio

Comment 4 Steve Sakoman 2023-01-25 14:36:20 UTC

Dunfell occurrence:

https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/6514

qemuppc fedora36-ty-2

Comment 5 Randy MacLeod 2023-06-15 14:56:16 UTC

Dunfell specific and hasn't happened in 6 months.