Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prow cert is expired? #150

Closed
bobcatfish opened this issue Dec 10, 2019 · 2 comments
Closed

Prow cert is expired? #150

bobcatfish opened this issue Dec 10, 2019 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@bobcatfish
Copy link
Contributor

Expected Behavior

https should work for prow.tekton.dev

Actual Behavior

As pointed out by @chmouel when you visit prow.tekton.dev (e.g. https://prow.tekton.dev/log?job=pull-tekton-pipeline-unit-tests&id=1204443482555420674 to look at the raw build log for tektoncd/pipeline#1702) you see an error like this:

image

Additional Info

Everything we know about how the certs work is written at https://github.com/tektoncd/plumbing/tree/master/prow#ingress - also @dlorenc will know more if he wants to jump in here :D

p.s. as a follow up to fixing this immediate issue we should open an issue to proactively prevent this in the future (unless we feel its not worth the effort)

@vdemeester
Copy link
Member

/kind bug

This is fixed now, see #152
/close

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 13, 2019
@tekton-robot
Copy link
Contributor

@vdemeester: Closing this issue.

In response to this:

/kind bug

This is fixed now, see #152
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants