After last update, the plugin does not start new machines (or seems to be doing anything at all) #528
Comments
|
To extend @ohadcohenanjuna description: Got same behaviour. Issue seems to be in validation of template: Any suggestions ? |
|
we started also having the same issue after the last plugin update which was introduced by #507 |
|
Any specific steps to reproduce or key types needed? |
|
we are using ssh keys generated by ssh-keygen ( rsa key 4096 bytes ) |
|
I've tried with:
On each of them I've tried:
I didn't hit any issues Is it possible to create a minimal reproduction? I've tried this on: Java 11 and Java 21 |
|
Could you provide a full plugin list? Its possible you have a dependency conflict and the dependency update exposed it. I can't see any other plugin using this dependency though |
|
I can't post it publicly here for security reasons :( |
|
this is a list of plugins where we have seen the issue and this is an SBOM of the jenkins image: |
|
Thanks I’ll try reproduce with that list ~next week |
|
I wasn't able to reproduce it with that list =/ |
|
In addition to @ysmaoui maybe there could be an issue with the specific template used as casc: jenkins:
clouds:
- azureVM:
azureCredentialsId: "az-vm-sp"
deploymentTimeout: 1200
existingResourceGroupName: "rg-test-1"
maxVirtualMachinesLimit: 16
name: "VM-Cloud"
resourceGroupReferenceType: "existing"
vmTemplates:
- templateName: "docker"
builtInImage: "Ubuntu 22.04 LTS"
credentialsId: "ssh-jenkins"
diskType: "managed"
doNotUseMachineIfInitFails: false
executeInitScriptAsRoot: false
existingStorageAccountName: "satestjenkinsjj001"
imageReference:
galleryImageDefinition: "docker"
galleryImageSpecialized: true
galleryImageVersion: "1.0.0"
galleryName: "sig_test_jenkins"
galleryResourceGroup: "rg-test-1"
gallerySubscriptionId: "xxx hidden xxx"
imageTopLevelType: "advanced"
installGit: true
javaPath: "java"
labels: "docker"
launcher:
ssh:
sshConfig: |-
Host 192.168*
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
location: "West Europe"
maxVirtualMachinesLimit: 4
maximumDeploymentSize: 4
noOfParallelJobs: 1
osDiskSize: 512
osDiskStorageAccountType: "Standard_LRS"
osType: "Linux"
retentionStrategy: "azureVMCloudOnce"
storageAccountNameReferenceType: "existing"
storageAccountType: "Standard_LRS"
subnetName: "snet-jenkins-vms"
usageMode: NORMAL
usePrivateIP: true
virtualMachineSize: "Standard_F16s_v2"
virtualNetworkName: "vnet-jenkins-test"
virtualNetworkResourceGroupName: "rg-test-1"
tags:
- name: "JenkinsVMType"
value: "docker" |
|
I had the same problem with plugin version 933.v440f85ced646 |
|
Hi, as an update, it seems like the new agent version released a few days ago does work. So this might be able to be resolved. |
|
Interesting, thanks for the update |
|
Hi @timja, we are still getting the issue with the latest version 948.v0b_47dc66677e it is working for us with 901.ved986df424b_3 any thoughts what could be the issue? Full stack trace |
|
No I spent awhile trying to reproduce it and was not able to. |
|
Hi I've found some workound for this issue. I was digging in the source code of plugin's dependency maverick-synergy and found the problematic line: maverick-synergy github. Path of this file is later evaluated and gives the null exception: In our jenkins instance I've set the system property: Maybe this can be useful for someone else or be a point for some further investigating on the issue Cheers! BTW we had this issue on:
|
Looks unnecessary: https://github.com/sshtools/maverick-synergy/blob/3.1.2/maverick-logging/src/main/java/com/sshtools/common/logger/DefaultLoggerContext.java#L110-L119 If the path doesn't exist then it should load with no configuration. Nice workaround find though. |
This could be very likely also a permission issue for some unhandled case of maverick. I suspect people who restrict the jenkins user a bit more will be hitting this issue. Also it should load with no configuration, but I think the error exactly comes on the check if the file exists: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jenkins and plugins versions report
Jenkins Version: Jenkins 2.440.3. (can confirm also a problem on 2.440.2)
Azure VM Agent: working: 901.ved986df424b_3
not working: 921.v76424a_e24594
What Operating System are you using (both controller, and any agents involved in the problem)?
Agents are Ubuntu machines; the controller is a docker image running on AWS Linux2. the docker image is: jenkins:lts-jdk21
Reproduction steps
After upgrade and restart of the Jenkins server, jobs are just waiting for agents but the plugin does not kick in, nothing in the logs (so it seems that the plugin is not seeing jobs are pending at all).
Expected Results
Agents would spin when jobs are pending,
Actual Results
nothing happens. no longs, just jobs in the queue and no new agents
Anything else?
Downgrading the plugin fixed the issue.
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: