Skip to content

[v1.5] CI: Provisioning fails with "Get https://k8s1:5000/v2/: x509: certificate has expired or is not yet valid" #11641

@joestringer

Description

@joestringer

v1.5 CI Provisioning

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3112/execution/node/74/log/

04:34:33      k8s1-1.15: Successfully built ff4f54edf696
04:34:33      k8s1-1.15: Successfully tagged cilium/cilium:latest
04:34:33      k8s1-1.15: echo "Push like this when ready:"
04:34:33      k8s1-1.15: Push like this when ready:
04:34:33      k8s1-1.15: echo "docker push cilium/cilium:"latest""
04:34:33      k8s1-1.15: docker push cilium/cilium:latest
04:34:33      k8s1-1.15: pushing container image to k8s1:5000/cilium/cilium-dev...
04:34:33      k8s1-1.15: Untagged: cilium/cilium:latest
04:34:33      k8s1-1.15: The push refers to repository [k8s1:5000/cilium/cilium-dev]
04:34:33      k8s1-1.15: Get https://k8s1:5000/v2/: x509: certificate has expired or is not yet valid
04:34:33  The SSH command responded with a non-zero exit status. Vagrant
04:34:33  assumes that this means the command failed. The output for this command
04:34:33  should be in the log above. Please read the output to determine what
04:34:33  went wrong.

This seems to affect all v1.5 CI runs in the latest backport (#11626).

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CIContinuous Integration testing issue or flakeneeds/triageThis issue requires triaging to establish severity and next steps.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions