Project

General

Profile

Actions

action #168091

closed

logwarn: "Publishing opensuse.openqa.job.done failed: SSL connect attempt failed"

Added by nicksinger about 1 month ago. Updated 8 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-10-10
Due date:
% Done:

0%

Estimated time:

Description

Observation

We received an e-mail from logwarn about the following errors in /var/log/openqa:

[2024-10-10T08:34:46.593842Z] [error] [pid:4744] Publishing opensuse.openqa.job.done failed: SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
[2024-10-10T08:34:47.611514Z] [error] [pid:4744] Publishing opensuse.openqa.job.done failed: SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
…
[2024-10-10T08:35:45.683230Z] [error] [pid:26453] Publishing opensuse.openqa.job.done failed: SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
[2024-10-10T08:35:46.012665Z] [error] [pid:24209] Publishing opensuse.openqa.job.done failed: SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

the direct issue seems to be gone but I can't even verify or understand what is wrong because the error message lacks details. So at the very least it should be improved (e.g. which host it tried to connect to? What FQDN?)

Suggestions

  • The opensuse part suggests this is rabbit.opensuse.org
  • Disambiguate the log message to clarify if this is an issue on e.g. the openQA side or somewhere else?
    • See lib/OpenQA/WebAPI/Plugin/AMQP.pm
  • Add the message to the blocklist? - Better not as these error message could in general be actionable for us.

Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #169690: logwarn repeatedly sending openssl related problems. Is the state file stuck?Resolvedokurz2024-11-11

Actions
Actions #1

Updated by ybonatakis about 1 month ago

  • Tags set to infra
  • Category set to Regressions/Crashes
  • Target version set to Tools - Next
Actions #2

Updated by jbaier_cz about 1 month ago

"Publishing opensuse.openqa.job.done failed" looks like amqp messages, i.e. that would be connection to rabbit.opensuse.org.

Actions #3

Updated by okurz about 1 month ago

  • Tags changed from infra to o3, ssl
  • Target version changed from Tools - Next to Ready
Actions #4

Updated by mkittler about 1 month ago

Yes, for o3 it would be rabbit.opensuse.org and for OSD rabbit.suse.de. It is basically what's in the url field of the [amqp] section of openqa.ini.

Actions #5

Updated by okurz about 1 month ago

  • Description updated (diff)
  • Status changed from New to Rejected
  • Assignee set to okurz

in theory we could add the FQDN in the log message but during the estimation call we decided that it's not worth the effort for such problem which is not likely to reappear anytime soon.

Actions #6

Updated by ybonatakis 8 days ago

  • Status changed from Rejected to Workable

I reopened it as there are a batch of new emails for that issue

Actions #7

Updated by okurz 8 days ago

  • Status changed from Workable to New
  • Assignee deleted (okurz)
Actions #8

Updated by jbaier_cz 8 days ago

In the early morning openssl s_client -connect rabbit.opensuse.org:amqps showed expired certificate; it looks good now and actually the presented certificate is not entirely new, maybe there was a missed reload after renewal like we saw in #169078

Actions #9

Updated by okurz 8 days ago · Edited

  • Status changed from New to Resolved
  • Assignee set to okurz

Right. Thanks for looking into this. No more problem observed. Although no clear solution was stated by according administrators. I also asked in https://app.element.io/?updated=1.11.69#/room/#admin:opensuse.org within message https://matrix.to/#/!wZwXBKKJqHykbBnWhM:opensuse.org/$Lstp16Fy6kJnF75aPPqkrRB2f9DBdy6iYnmkLT9Pvi0 and got a response pointing to #168487

Actions #10

Updated by tinita 7 days ago

  • Related to action #169690: logwarn repeatedly sending openssl related problems. Is the state file stuck? added
Actions

Also available in: Atom PDF