HTTP GET and POST requests to https://mbs.mbox.centos.org/module-build-service/1/module-builds/ are raising SSL exceptions in Python.
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1123)
Curl also raises an SSL error.
$ curl https://mbs.mbox.centos.org/module-build-service/1/module-builds/ curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mbs.mbox.centos.org:443
This worked as recently as 2021-05-06, which was the last time I built a module. Until this is resolved we cannot build modules for CL8 or CS8.
Let's as the only person having access (and who deployed) it
Metadata Update from @arrfab: - Issue assigned to bstinson - Issue tagged with: centos-stream
FWIW, I just tested this and it seems cert for console itself has expired :
echo "" |openssl s_client -connect mbox.centos.org:8443 -showcerts| sed -n '/BEGIN CERTIFICATE/,/END CERT/p' |openssl x509 -text -noout|grep -A 2 Validity depth=1 CN = openshift-signer@1557174782 verify error:num=19:self signed certificate in certificate chain DONE Validity Not Before: May 6 20:33:03 2019 GMT Not After : May 5 20:33:04 2021 GMT
It's an openshift 3.x cluster
Don't know if that's related but now even kojihub doesn't seem to answer : https://koji.mbox.centos.org just show a httpd index dir (probably falling back to kojifiles vm)
https://pagure.io/centos-infra/issue/325 Potentially related
https://mbs.mbox.centos.org is responding now but rejects all requests for module builds.
{'error': 'Bad Request', 'message': 'No dependency combination was satisfied. Please verify the buildrequires in your modulemd have previously been built.', 'status': 400}
The error doesn't make sense because all the buildrequirements in question are available and mbs knows about them.
per discussion with @bstinson , this ticket can be closed as service is up and running
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Just to be clear, we're closing this because the infra component is done. Still looking into the module depsolving issue that's still ongoing.
Login to comment on this ticket.