Deployments failing due to “Jenkins doesn’t have label ‘java-python’”

Community
1

Deployments failing due to “Jenkins doesn’t have label ‘java-python’”

I’m seeing a recurring Jenkins pipeline failure where the job reports:

“Jenkins doesn’t have label ‘java-python’”

The pipeline then defaults to the controller node, which does not have the expected tools or environment. This ultimately causes the build to fail.

Started by user unknown or anonymous
Obtained Jenkins/pipeline.groovy from Git repository

[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins controller in workspace

[Pipeline] checkout
Selected Git installation does not exist. Using Default
The recommended git tool is: NONE
Using credential ****
Fetching changes from remote Git repository
Checking out revision <redacted>

[Pipeline] stage (Download Workspace)
Downloading artifact:
curl -kv https://<artifact-repo>/repository/.../artifact.zip -o artifact.zip
...
HTTP/1.1 200 OK
Content-Type: application/zip
Content-Length: <redacted>

Download completed.

[Pipeline] stage (Process Workspace)
Unzipping artifact.zip
Extracted:
 - content/file.yml
 - metadata.json

RMQ Broker Name: <redacted>
Broker Domain: <redacted>
OCP Project: <empty>
OCP Cluster: <empty>

[Pipeline] stage
SKIP REMAINING STAGES: true

Error when executing post condition:
java.lang.Exception: FAILED BUILD
...
End of Pipeline
Finished: FAILURE





We are suspecting the current version of Jenkins 2.346.3 core and openshift plugin are making vulnerabilities. We suspect this is the cause of jenkins not connecting to OpenShift. could someone please check and advise

OpenShift Login Plugin 1.0.27
Open redirect vulnerability
Session fixation vulnerability


OpenShift Login
Version1.0.27
Allows you to log in to Jenkins via OAuth to an OpenShift installation
Report an issue with this plugin
Warning: The currently installed plugin version may not be safe to use. Please review the following security notices:
Open redirect vulnerability
Session fixation vulnerability
2

That may indicate that you have a controller that has executors defined on it. In general, that is a bad configuration. Refer to the Jenkins documentation for the reasons why that is a bad configuration. Please read and follow the instructions in the “Controller Isolation” documentation.

You are running a Jenkins version that is many years out of date. It has many known critical security vulnerabilities. It is no longer supported by the Jenkins update center. It is unlikely that others will be able to help you with that outdated version.

Plan your upgrade to the most recent version of Jenkins.

Refer to the blog post describing Jenkins upgrades for more details.