-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node failed to run because of X.509 certificate error #9133
Comments
do we have enough logs to investigate this one ? i.e. printout of each certificate ? to see what we have missing here, and why ? if not we should introduce those kind of logs, for catching this next time. |
Collect TLS/SSL artifacts (server, client certificates; CA certificate; etc.) and keep them after a test is finished, similarly to how logs are collected and published. This will facilitate root cause analysis of SCT failures caused by certificate related issues. Closes: scylladb#9133
Collect TLS/SSL artifacts (server, client certificates; CA certificate; etc.) and keep them after a test is finished, similarly to how logs are collected and published. This will facilitate root cause analysis of SCT failures caused by certificate related issues. Closes: scylladb#9133
The reason for the issue is known and the fix #8066 addresses it. But the test was executed from the branch But to facilitate certificates related issues analysis the PR #9219 introduces a change, so that TLS/SSL artifacts created during a test are collected (and published to Argus). |
Collect TLS/SSL artifacts (server, client certificates; CA certificate; etc.) and keep them after a test is finished, similarly to how logs are collected and published. This will facilitate root cause analysis of SCT failures caused by certificate related issues. Closes: scylladb#9133
Collect TLS/SSL artifacts (server, client certificates; CA certificate; etc.) and keep them after a test is finished, similarly to how logs are collected and published. This will facilitate root cause analysis of SCT failures caused by certificate related issues. Closes: scylladb#9133
Test: https://jenkins.scylladb.com/job/scylla-staging/job/amnon/job/longevity-100gb-4h-test/9/ failed
The reason, a node failed with the following error:
11:26:16 2024-11-05T09:20:31.616+00:00 longevity-100gb-4h-allow-pr-db-node-9fdeb40d-5 !ERR | scylla[6924]: [shard 0:main] init - Startup failed: std::system_error (error GnuTLS:-62, Unknown Subject Alternative name in X.509 certificate.)
The text was updated successfully, but these errors were encountered: