You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller: Ubuntu 20.04
Azure Agents: Windows 10
Reproduction steps
Configure Azure Cloud
Create New Azure Cloud and a Template
In template, Select "Advanced" so that it enables usage of Image Gallery and the "Launch method" field.
Leave the default launch method as "Launch agents via SSH".
Verify template and then goto Manage Jenkins->Configuration as Code->View Configuration
You will see that the "launcher: ssh" attribute is not there.
Expected Results
The JcasC "launcher: ssh" attribute should be generated when the default "Launch agents via SSH" launch method is being used in the advanced mode.
So that when you click on the Manage Jenkins->Configuration as Code->View Configuration button your template will have the launcher attribute. The plugin's README mentions doing this to get your initial JCasC template.
Actual Results
As long as "launcher: ssh" isn't in our JcasC configuration, occasionally Jenkins forgets it is supposed to use the default SSH and instead uses JNLP. What we see is the agent never connects via SSH and the plugin times out the agent
The only way I figured this out was looking at the System Log for Azure when my agents would connect to the AVM. The system log showed
...
...
Sep 24, 2024 2:03:30 PM INFO com.microsoft.azure.vmagent.AzureVMCloud$2 call
Adding agent emb3ef890 to Jenkins nodes
Sep 24, 2024 2:03:30 PM INFO com.microsoft.azure.vmagent.AzureVMCloudRetensionStrategy start
Starting azureComputer emb3ef890
Sep 24, 2024 2:03:30 PM INFO com.microsoft.azure.vmagent.AzureVMCloud waitUntilJNLPNodeIsOnline
Azure Cloud: waitUntilOnline: for agent emb32os3ef890
Once I explicitly added "launcher: ssh" to my JcasC template it worked 100% of the time and I have not seen the issue since.
Anything else?
No response
Are you interested in contributing a fix?
I can test any release candidates to verify the issue is fixed
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller: Ubuntu 20.04
Azure Agents: Windows 10
Reproduction steps
You will see that the "launcher: ssh" attribute is not there.
Expected Results
The JcasC "launcher: ssh" attribute should be generated when the default "Launch agents via SSH" launch method is being used in the advanced mode.
So that when you click on the Manage Jenkins->Configuration as Code->View Configuration button your template will have the launcher attribute. The plugin's README mentions doing this to get your initial JCasC template.
Actual Results
As long as "launcher: ssh" isn't in our JcasC configuration, occasionally Jenkins forgets it is supposed to use the default SSH and instead uses JNLP. What we see is the agent never connects via SSH and the plugin times out the agent
The only way I figured this out was looking at the System Log for Azure when my agents would connect to the AVM. The system log showed
Once I explicitly added "launcher: ssh" to my JcasC template it worked 100% of the time and I have not seen the issue since.
Anything else?
No response
Are you interested in contributing a fix?
The text was updated successfully, but these errors were encountered: