Hi,

The certificates on gerrit.cloudera.org have been fixed, so the Jenkins
service is fully functional again.

As always, please let me know if you experience any issues.

Thank you,

  - LaszloG

On Fri, Feb 16, 2024 at 7:38 PM Laszlo Gaal <laszlo.g...@cloudera.com>
wrote:

> The Jenkins service is up and running with limited functionality at this
> time:
> only the precommit jobs that are based on Ubuntu 20.04 are guaranteed to
> be available.
>
> The outage is caused by a misconfigured certificate chain that has been
> installed on gerrit.cloudera.org during its certificate renewal process,
> which prevented Jenkins, and its workers from completing the TLS handshake
> with Gerrit. Popular browsers are able to survive this condition, so the
> Gerrit UI is still working.
>
> I have installed a workaround that allows worker instances based Ubuntu
> 20.04 to connect to Gerrit in order to keep precommit functionality
> available; gerrit-auto-critic, gerrit-code-review-checks and
> gerrit-verify-dryrun are all working again.
> However, no other jobs are guaranteed to be able to connect to
> gerrit.cloudera.org until the certificate problem is resolved on
> that server.
>
> Jobs can still be run against Github, or Apache Gitbox, connectivity to
> those services were not impacted.
>
> Updates will be sent out on the mailing list.
>
>
> Thank you for your patience,
>
>   - LaszloG
>
> PS: if you really, really need something that is still broken right now,
> please reach out to me directly, or on the mailing list.
>
> On Fri, Feb 16, 2024 at 2:49 PM Laszlo Gaal <laszlo.g...@cloudera.com>
> wrote:
>
>> Hi,
>>
>> The upstream Jenkins instance seems to have problems connecting to the
>> Impala project's Gerrit instance at gerrit.cloudera.org since the
>> latter's certificate was renewed earlier today. Initial symptoms suggest
>> that the new certificate's issuer is not present in the trusted CA set of
>> jenkins.impala.io.
>>
>> The problem is being investigated; mail will be sent when the service
>> becomes available again.
>>
>> My apologies for the disruption,
>>
>>   - LaszloG
>>
>

Reply via email to