Pod init fails due to unbound variable JENKINS_UC
Summary
Encountering a "CrashLoopBackoff" condition in pod init phase
Steps to reproduce
helm install jenkins-dev .
What is the current bug behavior?
On helm install and/or upgrade
- getting a "CrashLoopBackoff" condition in pod init phase
identifying message:
- /usr/local/bin/install-plugins.sh: line 248: JENKINS_UC: unbound variable
What is the expected correct behavior?
No CrashLoopBackoff in pod init phase
Relevant logs and/or screenshots
Console commands and output
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
jenkins-dev-0 0/2 Init:CrashLoopBackOff 1 46s
jenkins-dev-ingress-nginx-controller-68bdc65bd9-r4cn2 1/1 Running 0 118d
$ kubectl logs jenkins-dev-0 -c init
disable Setup Wizard
download plugins
Creating initial locks...
Analyzing war /usr/share/jenkins/jenkins.war...
Registering preinstalled plugins...
/usr/local/bin/install-plugins.sh: line 248: JENKINS_UC: unbound variable
Possible fixes
Either:
- Update Dockerfile to include ENV variable/value for JENKINS_UC
- Add JENKINS_UC variable/value within values.yaml used for helm install/upgrade:
envVars:
- name: JENKINS_UC
value: https://updates.jenkins.io
Defintion of Done
-
Bug has been identified and corrected within the container
/cc @ironbank-notifications/bug
Edited by Ghost User