| Summary: | AB-INT: ssh.SSHTest.test_ssh fails with "No route to host" | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Alexandre Belloni <alexandre.belloni> |
| Component: | oeqa/runtime | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | alexandre.belloni, chee.yang.lee, mathieu.dubois-briand, randy.macleod, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandre Belloni
2023-12-16 23:20:55 UTC
RP investigated and said: 10:13:53 RP | abelloni: can you see a timestamp for when it happened 10:13:54 RP | ? 10:14:35 abelloni | 1702627323 10:14:52 abelloni | $ LC_TIME=C date -u -d @1702627323 10:14:55 abelloni | Fri Dec 15 08:02:03 UTC 2023 10:15:29 abelloni | Thu Dec 14 23:11:30 UTC 2023 10:15:37 abelloni | between those times 10:16:33 RP | at 6:24 there is a systemd-networkd-wait-online: Timeout occurred waiting for network connectivity 10:18:50 RP | was part of an apt update. Nothing else I can see 10:22:13 RP | abelloni: I think networkd probably did something :/ https://autobuilder.yoctoproject.org/typhoon/#/builders/93/builds/1831/steps/12/logs/stdio qemuarm64-ptest-fast ubuntu2204-arm-1 This one was running between: Fri Dec 15 01:07:14 UTC 2023 Fri Dec 15 03:12:39 UTC 2023 https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5869/steps/12/logs/stdio ubuntu2204-arm-1 qemuarm64-ptest https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5869/steps/12/logs/stdio qemuarm64-ptest ubuntu2204-arm-1 Just looks like the networking went dead. Systemd-networkd notes a change in carrier but it's not clear if our log message happens before that log. Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3. Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone. no-x11 debian12-ty-1 https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9549/steps/15/logs/stdio oe-selftest-debian debian11-vk-2 https://valkyrie.yoctoproject.org/#/builders/35/builds/176/steps/14/logs/stdio oe-selftest-debian debian11-vk-3 https://valkyrie.yoctoproject.org/#/builders/35/builds/178/steps/14/logs/stdio oe-selftest-debian debian11-vk-2 https://valkyrie.yoctoproject.org/#/builders/35/builds/182/steps/14/logs/stdio oe-selftest-debian debian11-vk-2 https://valkyrie.yoctoproject.org/#/builders/35/builds/229/steps/14/logs/stdio oe-selftest-debian debian11-vk-3 https://valkyrie.yoctoproject.org/#/builders/35/builds/238/steps/14/logs/stdio The debian11 issues should be fixed by changing to the 6.1 kernel. Waiting to see if debian12 happens again. No recurrences reported so closing. |