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

Kubernetes Plugin does not load properly on first start #23

Open
mertel-rh opened this issue May 21, 2020 · 1 comment
Open

Kubernetes Plugin does not load properly on first start #23

mertel-rh opened this issue May 21, 2020 · 1 comment

Comments

@mertel-rh
Copy link
Contributor

On OCP 3.11 using the Helm chart to deploy Jenkins s2i-config-jenkins when Jenkins starts up the Kubernetes Plug-In settings are not available or usable until after applying an update and restarting.

After deploying the chart and letting Jenkins spin up from the s2i build:
Navigate to Jenkins -> Manage Jenkins -> Configure System
The "Cloud" section provided by Kubernetes Plugin is not present as expected
Reviewing the Plugins settings show the plug-in listed but it is greyed out with an update available.
Apply updates and let Jenkins restart
Navigate back to the Configure System settings page and the "Cloud" section is now present and populated with the expected information

Preferred behavior would be for the plugin to function after the s2i-build without requiring an update/restart cycle

@pabrahamsson
Copy link
Contributor

@springdo I've worked with @mertel-rh and verified that this is also the case on OCP 4.4 (except when I update the plugin Jenkins never comes back up) with both v1.6 & v1.7 of this repo. I've tested with the Jenkins chart in UJ (which should use the Helm chart mentioned here) and also with a straight up oc new-build ..., same result.
However, with "vanilla" jenkins-ephemeral all seems normal.

Jenkins pipelines are working fine, it just appears that the "Cloud" section is missing from the configuration as described above.
Is this something you're aware of or have any ideas on how to troubleshoot?

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