Actions
action #180080
closedcoordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #154771: [epic] Improved test developer user experience
o3 logreports - Publishing opensuse.openqa.job.restart failed: Connect timeout (0 attempts left)
Start date:
2025-04-06
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
We see the following errors on o3:
# /var/log/openqa
[2025-04-06T12:56:59.837721Z] [error] [pid:24932] Publishing opensuse.openqa.job.done failed: Connect timeout (event ID: 4975492, 0 attempts left)
It happened for some hours on saturday
[2025-04-05T09:15:08.186238Z] [error] [pid:25129] Publishing opensuse.openqa.job.done failed: Connect timeout (event ID: 4971354, 0 attempts left)
...
[2025-04-05T13:04:06.080452Z] [error] [pid:32436] Publishing opensuse.openqa.comment.update failed: Connect timeout (event ID: 735273, job ID: 4972182, 0 attempts left)
and sunday
[2025-04-06T02:43:30.844681Z] [error] [pid:24038] Publishing opensuse.openqa.job.done failed: Connect timeout (event ID: 4973629, 0 attempts left)
...
[2025-04-06T12:56:59.837721Z] [error] [pid:24932] Publishing opensuse.openqa.job.done failed: Connect timeout (event ID: 4975492, 0 attempts left)
rabbit.opensuse.org was pingable during that time from o3, https://rabbit.opensuse.org/ showed incoming events in general, and also publishing succeeded in between.
Updated by tinita about 1 month ago
- Copied from action #105903: o3 logreports - Publishing opensuse.openqa.job.restart failed: Connect timeout (9 attempts left) added
Updated by okurz about 1 month ago
- Tags set to reactive work
- Category set to Regressions/Crashes
Updated by livdywan about 1 month ago
- Related to tickets #180059: registry.opensuse.org problem: "Error response from daemon: Get "https://registry.opensuse.org/v2/": net/http: TLS handshake timeout" added
Updated by tinita about 1 month ago
So we think this was related to #180059 and we were alerted because openqa couldn't reach the amqp server for a long time, so this is actually expected in such a case. Therefor resolving
Actions