-
Notifications
You must be signed in to change notification settings - Fork 235
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
Jenkins Master Boot Loop #571
Comments
Trying the latest build
|
Nightly build is not compatible with most recent released (0.4.3) version of the Helm chart. We've managed to get the operator and Jenkins working on minikube with kubernetes 1.20.7, most recent released Helm chart (chart v.0.4.3 with operator v0.5.0) by providing values.yaml with updated basePlugin versions (see below, they're the same as in master branch's Helm chart), and deleting the crds mentioned before, but this issue on kubernetes 1.20.7 might be AKS-specific (e.g. if AKS sets Contents of values.yaml we've used:
|
Tried with the chart on master and latest image:
|
Could you paste here the output of |
@Sig00rd sorry for the delay.
|
The above output is using the latest |
This is the operator logs:
|
We are seeing the same issue with our EKS cluster (1.19.6). |
+1 completely broken also appears to be duplicate RBAC roles and bindings |
Did you delete old CRDs and apply new ones before upgrading from Operator version 0.5.0? |
Upgrading the
|
thanks i did see that but it was targetted at openshift users from how i read the message in the releases. Will try again |
I've edited the release notes – it should be clearer now 🙂 |
Thanks.. ps.. usually with a crd change the jenkins.io/v1alpha2 gets bumped? |
hmm ok so all spins up but now hitting
infinite.. service is up but the jsasc does not trigger Thanks for the support btw and the app its a step up for sure :) Perhaps related to
this is a |
With regards to the CRD version, normally it would be bumped. This time there were no breaking changes in the actual API, we assumed that it would work, reality proved otherwise and we have to roll with it. Also, that's an alpha version, meaning that there may be breaking changes happening, once a more "stable" API release comes out it will have to be backward compatible to some degree. Non-RSA SSH keys are fixed. Make sure your names are correct (
For reference: https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration/ |
Thanks jsut fyi this is a cluster thats been up and working fine for a good 4 months; so the keys themselves and the setup is fine :) was just hoping to use a newer ssh-keygen to keep up to date with ssh-keygen progress |
FYI:
|
Thanks to the hints here and in #586 I was able to sort out my crash loop after upgrading 0.4.0 -> 0.6.0. I had extra volumes configured in the Jenkins object that had to be removed. It was triggering an out-of-sync crash loop just like how extra environment variables are triggering crash loops. |
Closing this as it seems resolved. Thanks for your contributions everyone! |
Describe the bug
The Jenkins master pod restarts every second. This id due to the operator detecting a environment change. I'm not sure if this is a duplicate of #570 but my Kubernetes version is different.
To Reproduce
Additional information
Kubernetes version: 1.20.7
Jenkins Operator version: 0.4.3
Platform: AKS
Add error logs about the problem here (operator logs and Kubernetes events).
Operator Logs
Events Log
The text was updated successfully, but these errors were encountered: