Closed sanjaysrikakulam closed 2 months ago
Ping @lopiola, can you clarify whether any certificate-related changes took place related to your S3?
Hello,
this is unexpected, I can ask our admins if there were any problems with the infrastructure yesterday night.
It seems to work all right now...
curl https://s3p.cloud.cyfronet.pl -v
...
* Server certificate:
* subject: C=PL; ST=Ma\U0142opolskie; O=Akademickie Centrum Komputerowe CYFRONET AGH; CN=*.s3p.cloud.cyfronet.pl
* start date: Sep 5 00:00:00 2023 GMT
* expire date: Sep 4 23:59:59 2024 GMT
* subjectAltName: host "s3p.cloud.cyfronet.pl" matched cert's "s3p.cloud.cyfronet.pl"
* issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4
* SSL certificate verify ok.
@lopiola Please check with your admins and let us know. In the meantime, when time permits, I will write a small script to test whether it works. The problem could be even in your identity management software layer as well.
There were SSL certificate-related issues during the set metadata step of jobs. After communicating this with Cyfronet, enable it.
The error log: https://gist.github.com/bgruening/9fc669ab7922118ed4857ccdbfa3619f
Marius said, "The entire object store configuration is initialized when using extended metadata". Therefore, even when the ObjectStore's
weight
was set to0
, the S3 store was initialized.