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

jx-bot-token shows Healthy=false #19

Open
jtfogarty opened this issue Nov 2, 2020 · 3 comments
Open

jx-bot-token shows Healthy=false #19

jtfogarty opened this issue Nov 2, 2020 · 3 comments

Comments

@jtfogarty
Copy link

I wanted to change the token used for jx git operator

jx admin operator succeeded as can be seen below but the health check still show healthy=false in Octant and

jx health get status --all-namespaces --watch shows

NAME                          NAMESPACE                     STATUS                        ERROR MESSAGE
jx-bot-token                  jx                            ERROR                         failed to verify bot account with https://api.github.com/user, response status 401 Unauthorized code 401
changing to the jx namespace to verify
jx ns jx
Now using namespace 'jx' on server ''.
jx verify ingress -b
now verifying docker registry ingress setup in dir .
jx gitops webhook update --warn-on-fail
W1102 13:39:26.780733    2046 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Checking hooks for repository jtf-ops/jx3-20201023
Found matching hook for url http://hook-jx.jx.docure.ai/hook
boot Job pod jx-boot-500f167bc44fda69928bce3-l64cg has Succeeded
boot Job jx-boot-500f167bc44fda69928bce3 has Succeeded
@rawlingsj
Copy link
Contributor

the health check uses the token from the tekton git secret

so my guess is that secret still has the old token. Are you able to confirm using

kubectl get secret tekton-git -oyaml

and base64 -D the password value?

@jtfogarty
Copy link
Author

@rawlingsj Correct, this show an old token.
Looking in Octant and the Jenkins X Plugin > Helm > jxgo in the jx-git-operator I see the correct token

@jtfogarty
Copy link
Author

What would it take to modify this test to validate the boot and pipeline secrets?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants