Issue switching to another cluster about jenkins-client-plugin HOT 5 CLOSED

Did you adjust the server cert authority as needed in the cluster config you changed?

Can you provide a snapshot of the cluster configuration from the Jenkins UI, as well as the pipeline script snippet where you reference that cluster via openshift.withCluster?

That error indicates it fell back to attempting to find a cert from the default location. Either your withCluster reference was such that we could not find the cluster, or we did not have a valid cert in the cluster configuration that was found.

from jenkins-client-plugin.

Hi, I didn't add any specific cert authority neither for the old cluster nor the new one. But why is trying to find certificate for the old cluster? IF I switch back to old cluster then it works.

This is my withCluster snippet

withEnv(["PATH+OC=${ocDir}/openshift-origin-client-tools-v3.6.0-c4dd4cf-linux-64bit","SKIP_TLS=true","https_proxy=http://b2b-http.dhl.com:8080"]) {
// Name of cluster configuration and user token. It is recommended to use a service account instead of your personal user.
openshift.withCluster( 'example', "${token}" ) {

from jenkins-client-plugin.

Well, in your original description, I don't see the --insecure-skip-tls-verify option I would expect to see if you are skipping TLS, which you would need to do if you are not adding any certs as you say. If that is not there, and you don't have a cert in your cluster config, that would explain why as a last resort it attempts to look at the default location. That is why the oc invocation fails.

As an aside, I see you have set SKIP_TLS in you envs ... in case you were wondering, that is not an env honored by this plugin.

But the disable tls verify on the cluster config you pasted is checked, which should add --insecure-skip-tls-verify; either that setting isn't getting propagated, or it is inadvertently getting unchecked when you are switching things around.

I'll need to make some time (should be Friday or Monday) to first try something similar and make sure nothing unexpected is happening. Otherwise, I might need to give you a debug plugin to try to explicitly print out the various settings as your are switching things around to see why your skip tls setting is getting lost.

from jenkins-client-plugin.

Thanks, now it is working with the skip tls. I didn't try with that checked. Still it is working in old Jenkins instance but in the new one I get the status -2

from jenkins-client-plugin.

ok good thanks for the confirm ... we'll track the -2 with the other issue you've got on that

from jenkins-client-plugin.