Common Problems

This document lists problems most frequently occurring when using Carthago Operator for Jenkins, and how to solve them.

Jenkins Pod keeps restarting with “missing-plugins” errors.

Jenkins can lose compatibility with its plugins or their dependencies.

If you want to reduce the probability of this happening:

  • Use a set version of Jenkins image instead of latest tag.

  • Declare plugins and all their dependencies in the Jenkins Custom Resource under plugins. If you are not sure which plugins to pin, you can check the logs from the initial-config init container or jenkins-controller container of Jenkins Pod. You can learn how to do that on Troubleshooting section

Also, Plugin Snapshot feature of the Operator makes it easier to avoid issues with plugins. You can read more about it here.

Jenkins Pod keeps restarting, not going past Init status

If your Jenkins Pod keeps restarting, and you can see statuses like Init:CrashLoopBackOff or Init:Error when you kubectl get the Pod, it points to an error during initial configuration of Jenkins. It typically happens as a result of passing mistyped configuration (for instance, plugin names) to Jenkins Custom Resource.

To find out the case of this error, check logs from initial-config init container of your Jenkins Pod. You can learn how to do that on Troubleshooting section

My job fails saying I don’t have the necessary permissions.

You can always add a custom Role for your Jenkins with the permissions you need and reference it in the Jenkins Custom Resource under spec.roles.

The Operator will create a RoleBinding for it.

Be careful. Operator may not have these permissions. As a quick temporary workaround, you can manually bind this role to the Operator service account.

I have added/updated the license Secret for the Operator, but the license verification did not trigger.

Currently, the license verification is not triggered by changes to the license Secret. To force a license check, delete the operator Pod. It will be automatically recreated and the verification will be performed again.

To learn how to add the license Secret, visit Installation guide.

In case of problems with licensing mechanism, looking through the logs from Operator’s Pod should help you find the source of the problem (the Secret was not found, it does not contain the correct information, the license key is invalid, etc.).