Github Actions failing due to TLS certificate expiration

Support Bug Fixes
1

Before submitting a topic, please confirm the following

[X ] I have searched for similar issues before creating this topic.
[ X] I have verified that my repository is using the Codecov GitHub app, if using GitHub
[ X] I have validated my codecov.yaml configuration file.
[ X] I have filled out the below sections to the best of my ability.

Description

Codecov is failing in github actions with TLS certification expiration error

CI/CD URL

Please provide a link to the CI/CD run.

Codecov Output

Run codecov/codecov-action@v2
  with:
    files: ./coverage/cover.out
    name: typesense-coverage
    verbose: true
  env:
    TYPESENSE_PORT: 8108
    TYPESENSE_API_KEY: xyz
    REDIS_PORT: 6379
    POSTGRES_USER: username
    POSTGRES_DB: default
    POSTGRES_PASSWORD: password
    ETCD_HOST: localhost
    ETCD_PORT: 2379
    REDSHIFT_PORT: 5439
    REDSHIFT_DATABASE: dev
    GOROOT: /opt/hostedtoolcache/go/1.17.12/x64
==> linux OS detected
Error: certificate has expired
    at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
    at TLSSocket.emit (events.js:314:20)
    at TLSSocket._finishInit (_tls_wrap.js:937:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12)

Expected Results

Coverage to be uploaded successfully

Actual Results

Workflow fails with a TLS error on upload

3 Likes
2

We are seeing this, too. Started circa 13:20 Pacific / 20:20 UTC on Tuesday.

3

For example: Prepare 0.9.1 release · contentauth/c2pa-rs@fab9652 · GitHub.

4

Same problem on our repo. We rely on this action in our CI integration, so it’s blocking our normal PR process.

5

We are seeing the same thing in self-hosted runner on GitHub.

6

This appears to be fixed now. Recent jobs are passing this step in our CI runs.

1 Like
7

Same here, our jobs started passing yesterday about the same time you reported.

8

Hey all,

Sorry I’m sorry we got to this a little late. The short version is that during regular maintenance we reprovisioned an SSL cert. Unfortunately, there was a window of time when uploader.codecov.com was serving the old cert. This, as you all have mentioned above has been resolved.

1 Like
9

This, as you all have mentioned above has been resolved.

@tom Error: certificate has expired - it is happening again.

10

Seeing the same thing again on our end

Error: certificate has expired
    at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
    at TLSSocket.emit (events.js:314:20)
    at TLSSocket._finishInit (_tls_wrap.js:937:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12)
11

same here

Run codecov/codecov-action@v2
==> linux OS detected
Error: certificate has expired
    at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
    at TLSSocket.emit (events.js:314:20)
    at TLSSocket._finishInit (_tls_wrap.js:937:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12)
12

Thanks, we’re investigating now. I’ll update here when we know more.

13

Hi all,

A routine change was made with our CDN provider which caused the old SSL certificate to be briefly served. This change has been rolled back and measures have been put in place to ensure changes of this nature do not happen again.

I’m sorry again for the issues you might have faced during these time periods.

14

working fine now.
thanks for updating us, tom.

1 Like