[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

26 views
Skip to first unread message

henti@geekware.co.za (JIRA)

unread,
Apr 17, 2018, 1:37:02 PM4/17/18
to jenkinsc...@googlegroups.com
Henti Smith created an issue
 
Jenkins / Bug JENKINS-50850
createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Issue Type: Bug Bug
Assignee: Azure DevOps
Components: azure-vm-agents-plugin
Created: 2018-04-17 17:36
Environment: Linux jenkins-master-01.internal 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux
Debian GNU/Linux 8 (jessie)

openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-1~bpo8+1-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)

Jenkins ver. 2.107.2 patched with https://github.com/jenkinsci/jenkins/pull/3354

Plugins:
metrics 3.1.2.11
pam-auth 1.3
pipeline-model-api 1.2.8
run-condition 1.0
pipeline-utility-steps 2.0.2
pipeline-github-lib 1.0
antisamy-markup-formatter 1.5
jquery 1.12.4-0
authentication-tokens 1.3
credentials-binding 1.16
icon-shim 2.0.3
pipeline-input-step 2.8
jquery-detached 1.2.1
github-branch-source 2.3.3
command-launcher 1.2
handlebars 1.1.1
matrix-project 1.13
resource-disposer 0.8
build-timeout 1.19
pipeline-model-definition 1.2.8
jackson2-api 2.8.11.1
copyartifact 1.39.1
scm-api 2.2.6
pipeline-stage-tags-metadata 1.2.8
PrioritySorter 3.6.0
pipeline-stage-step 2.3
azure-commons 0.2.5
email-ext 2.62
workflow-multibranch 2.17
gradle 1.28
workflow-cps 2.48
workflow-aggregator 2.5
workflow-api 2.27
script-security 1.43
cloudbees-folder 6.4
msbuild 1.29
git-server 1.7
ssh-agent 1.15
branch-api 2.0.19
promoted-builds 3.1
matrix-auth 2.2
pipeline-stage-view 2.10
workflow-cps-global-lib 2.9
ssh-credentials 1.13
ssh-slaves 1.26
timestamper 1.8.9
job-dsl 1.69
ant 1.8
workflow-scm-step 2.6
pipeline-graph-analysis 1.6
external-monitor-job 1.7
mailer 1.21
github-api 1.90
azure-credentials 1.6.0
windows-slaves 1.3.1
throttle-concurrents 2.0.1
conditional-buildstep 1.3.6
jsch 0.1.54.2
nodelabelparameter 1.7.2
maven-plugin 3.1.2
workflow-basic-steps 2.6
token-macro 2.5
rebuild 1.28
ws-cleanup 0.34
pipeline-rest-api 2.10
async-http-client 1.9.40.0
workflow-step-api 2.14
credentials 2.1.16
structs 1.14
ldap 1.20
git-client 2.7.1
docker-workflow 1.15.1
plain-credentials 1.4
mapdb-api 1.0.9.0
javadoc 1.4
github-organization-folder 1.6
ghprb 1.39.1-0-Semmle
github-oauth 0.29
azure-vm-agents 0.7.0
github 1.29.0
display-url-api 2.2.0
subversion 2.10.5
momentjs 1.1.1
parameterized-trigger 2.35.2
pipeline-model-declarative-agent 1.1.1
workflow-durable-task-step 2.19
pipeline-build-step 2.7
workflow-support 2.18
pipeline-milestone-step 1.3.1
groovy 2.0
jobConfigHistory 2.18
ace-editor 1.1
durable-task 1.22
pipeline-model-extensions 1.2.8
apache-httpcomponents-client-4-api 4.5.3-2.1
junit 1.24
docker-commons 1.11
build-alias-setter 0.4
git 3.8.0
workflow-job 2.19
bouncycastle-api 2.16.2
cloud-stats 0.18
lockable-resources 2.2
Priority: Minor Minor
Reporter: Henti Smith

After upgrading from 1.6.2 to 1.7.0 no VMs were being created. Investigation showed the changes in https://issues.jenkins-ci.org/browse/JENKINS-49150 affected us. Updated the credential and verified the template successfully. Saved and then VMs were being created, but no machine actually succeeded in being deployed. 

Logs contain : 

SEVERE: Failure creating provisioned agent 'jenkins-linux-8-core-build-slaveb939d10'
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d10 - Conflict - {error={code=OperationNotAllowed, message=Operation results in exceeding quota limits of Core. Maximum allowed: 350, Current in use: 344, Additional requested: 8. Please read more about quota increase at http://aka.ms/corequotaincrease.}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:612)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:854)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:832)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: check for jenkins-linux-8-core-build-slaveb939d10
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: jenkins-linux-8-core-build-slaveb939d10 doesnt exist
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate terminateVirtualMachine
INFO: Clean operation starting for jenkins-linux-8-core-build-slaveb939d10 NIC and IP
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate removeIPName
INFO: Remove NIC jenkins-linux-8-core-build-slaveb939d10NIC
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate removeIPName
INFO: Remove IP jenkins-linux-8-core-build-slaveb939d10IPName
Apr 17, 2018 12:55:18 PM hudson.slaves.NodeProvisioner$2 run
WARNING: Unexpected exception encountered while provisioning agent jenkins-linux-8-core-build-slave
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d10 - Conflict - {error={code=OperationNotAllowed, message=Operation results in exceeding quota limits of Core. Maximum allowed: 350, Current in use: 344, Additional requested: 8. Please read more about quota increase at http://aka.ms/corequotaincrease.}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:612)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:854)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:832)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

 This happened for all VMs being provisioned. After some minutes I disabled the plugin by changing the available labels to not include the requested label. 

I have also rolled back the plugin and this removed all my cloud configuration so had to recreate from scratch. 

Now the machines are starting up, but as soon as it's get added to jenkins, it gets (offline)  (suspended) and deleted after a couple of minutes. 

Logs : 

Apr 17, 2018 6:17:13 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeployment
INFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment jenkins-linux-8-core-build-slave0417181713767 with VM base name jenkins-linux-8-core-build-slave5a151
r 17, 2018 6:17:14 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeployment
INFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment jenkins-linux-8-core-build-slave0417181713767 in jenkins-slaves
Apr 17, 2018 6:17:26 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgent
INFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment jenkins-linux-8-core-build-slave0417181713767 to be completed
Apr 17, 2018 6:18:28 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgent
INFO: AzureVMCloud: createProvisionedAgent: Deployment jenkins-linux-8-core-build-slave0417181713767 not yet finished (Running): Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slave5a1510 - waited 60 seconds
Apr 17, 2018 6:19:16 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask cleanDeployments
INFO: AzureVMAgentCleanUpTask: cleanDeployments: Checking deployment jenkins-linux-8-core-build-slave0417181713767
Apr 17, 2018 6:24:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgent
INFO: AzureVMCloud: createProvisionedAgent: VM available: jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:24:07 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponse
INFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: 
found agent jenkins-linux-8-core-build-slave5a1510
OS type Linux
number of executors 1
Apr 17, 2018 6:24:31 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetails
INFO: Azure agent details:
nodeNamejenkins-linux-8-core-build-slave5a1510
adminUserName=be14c538-86a6-42db-b490-c3e936021e89
shutdownOnIdle=false
retentionTimeInMin=0
labels=linux-8core-scalable
Apr 17, 2018 6:24:31 PM com.microsoft.azure.vmagent.AzureVMCloud$4 call
INFO: Azure Cloud: provision: Adding agent jenkins-linux-8-core-build-slave5a1510 to Jenkins nodes
Apr 17, 2018 6:24:31 PM com.microsoft.azure.vmagent.AzureVMAgent createComputer
INFO: AzureVMAgent: createComputer: start for agent jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:24:31 PM com.microsoft.azure.vmagent.AzureVMCloudOnceRetentionStrategy start
INFO: AzureVMCloudOnceRetentionStrategy: start: azureComputer name jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:24:31 PM com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher launch
INFO: AzureVMAgentSSHLauncher: launch: launch method called for agent jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:24:55 PM com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession
INFO: AzureVMAgentSSHLauncher: getRemoteSession: getting remote session for user jenkins to host jenkins-linux-8-core-build-slave5a1510.westeurope.cloudapp.azure.com:22
Apr 17, 2018 6:24:56 PM com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession
INFO: AzureVMAgentSSHLauncher: getRemoteSession: Got remote session for user jenkins to host jenkins-linux-8-core-build-slave5a1510.westeurope.cloudapp.azure.com:22
Apr 17, 2018 6:25:39 PM com.microsoft.azure.vmagent.AzureVMCloudOnceRetentionStrategy done
INFO: AzureVMCloudOnceRetentionStrategy: Tagging VM to delete when idle: jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:27:13 PM com.microsoft.azure.vmagent.AzureVMCloudOnceRetentionStrategy done
INFO: AzureVMCloudOnceRetentionStrategy: Tagging VM to delete when idle: jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:29:13 PM com.microsoft.azure.vmagent.AzureVMCloudOnceRetentionStrategy done
INFO: AzureVMCloudOnceRetentionStrategy: Tagging VM to delete when idle: jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: check for jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: jenkins-linux-8-core-build-slave5a1510 exists
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$2 call
INFO: AzureVMAgentCleanUpTask: cleanVMs: deleting jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMAgent deprovision
INFO: AzureVMAgent: deprovision: Deprovision called for agent jenkins-linux-8-core-build-slave5a1510, for reason: Delete agent after build execution (when idle).
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: check for jenkins-linux-8-core-build-slave5a1510
Apr 17, 2018 6:29:16 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists
INFO: AzureVMManagementServiceDelegate: virtualMachineExists: jenkins-linux-8-core-build-slave5a1510 exists
Apr 17, 2018 6:29:28 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate terminateVirtualMachine

This means our azure infrastructure is not being utilised. 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

henti@geekware.co.za (JIRA)

unread,
Apr 17, 2018, 1:46:03 PM4/17/18
to jenkinsc...@googlegroups.com
Henti Smith updated an issue
Change By: Henti Smith
After upgrading from 1.6.2 to 1.7.0 no VMs were being created. Investigation showed the changes in https://issues.jenkins-ci.org/browse/JENKINS-49150 affected us. Updated the credential and verified the template successfully. Saved and then VMs were being created, but no machine actually succeeded in being deployed. 

Logs contain : 
{code:java}
{code}

 This happened for all VMs being provisioned. After some minutes I disabled the plugin by changing the available labels to not include the requested label. 

I have also rolled back the plugin and this removed all my cloud configuration so had to recreate from scratch. 

Now the machines are starting up, but as soon as it's get added to jenkins, it gets  
(offline)  (suspended) and deleted after a couple of minutes. 

Logs : 
{code:java}
{code}

This means our azure infrastructure is not being utilised. 

chenyl@microsoft.com (JIRA)

unread,
Apr 17, 2018, 7:22:02 PM4/17/18
to jenkinsc...@googlegroups.com
Chenyang Liu commented on Bug JENKINS-50850
 
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

From the logs, it seems you exceed the core limit in your subscription. Please add the quota limits


Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d10 - Conflict - {error={code=OperationNotAllowed, message=Operation results in exceeding quota limits of Core. Maximum allowed: 350, Current in use: 344, Additional requested: 8. Please read more about quota increase at http://aka.ms/corequotaincrease.}}

chenyl@microsoft.com (JIRA)

unread,
Apr 17, 2018, 7:23:02 PM4/17/18
to jenkinsc...@googlegroups.com
Chenyang Liu assigned an issue to Chenyang Liu
 
Change By: Chenyang Liu
Assignee: Azure DevOps Chenyang Liu

shanexpert28@gmail.com (JIRA)

unread,
Apr 18, 2018, 2:56:02 AM4/18/18
to jenkinsc...@googlegroups.com
shan shan started work on Bug JENKINS-50850
 
Change By: shan shan
Status: Open In Progress

henti@geekware.co.za (JIRA)

unread,
Apr 18, 2018, 4:42:02 AM4/18/18
to jenkinsc...@googlegroups.com
Henti Smith commented on Bug JENKINS-50850
 
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

Morning Chenyang Liu 

I'm terribly sorry, I seem to copy and pasted the wrong set of logs. Tho the logs above does indeed show up, and you're right it's a quota limit. 

 

Please see the below logs for the relevant information. 

Apr 17, 2018 12:54:02 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeployment
INFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment jenkins-linux-8-core-build-slave0417125402381 with VM base name jenkins-linux-8-core-build-slaveb939d
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMCloud$4 call
SEVERE: Failure creating provisioned agent 'jenkins-linux-8-core-build-slaveb939d7'
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d7 - Conflict - {status=Failed, error={code=ResourceDeploymentFailure, message=The resource operation completed with terminal provisioning state 'Failed'., details=[{code=AllocationFailed, message=Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.}]}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:612)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:854)
at com.microsoft.azure.vmagent.AzureVMCloud$4.call(AzureVMCloud.java:832)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Apr 17, 2018 12:55:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate terminateVirtualMachine
INFO: AzureVMManagementServiceDelegate: terminateVirtualMachine: Removing virtual machine jenkins-linux-8-core-build-slaveb939d7

We had 862 such failures in a space of 50 minutes while the plugin was active and trying to diagnose the problem. The original logs is likely as a result of this mass failures, so please consider it as such. 

 

I "disabled" the plugin by changing the label to a non existant one so VMs stopped being created as the race condition was in play. We had jobs that would trigger azure resources, but since the provisioning failed, was never met, which in turn kept triggering provisioning. 

 

Again I'm sorry for the mistake regarding the logs. 

chenyl@microsoft.com (JIRA)

unread,
Apr 18, 2018, 4:56:01 AM4/18/18
to jenkinsc...@googlegroups.com

Seems it's also a problem in Azure side. AllocationFailed

I don't know how large the size you chose. But you can do some tests to verify whether it's a plugin's problem or not. You can create the same size vm  through Azure Portal directly, and try to use plugin to provision VMs on the another region.

 

henti@geekware.co.za (JIRA)

unread,
Apr 18, 2018, 5:29:02 AM4/18/18
to jenkinsc...@googlegroups.com

Chenyang Liu

Thank you for that link, when restarting Jenkins was trying to start up a max of 40 VMs of size Standard_F8s_v2 which is 8 vcpus and 16GB Ram. 

We have 2 Standard_D2_v3 VM running for windows workers, which is 8 vcpus, 32 GB Ram. 

So that should have only been 336 vcpus. I'll play around with this. 

I'd also like to reitterate, that once I rolled back to 1.6.2, the problem went away and the plugin is working, so saying it's a resource limit issue does not make sense. The old verison of the plugin has exactly the same configuration (actually it's limited to 20 vms, not 40 like before) but still not seeing the issue above. 

chenyl@microsoft.com (JIRA)

unread,
Apr 18, 2018, 6:03:02 AM4/18/18
to jenkinsc...@googlegroups.com

You said "This happened for all VMs being provisioned". Is it means the plugin can't provision any VMs since restart? After restarting, are there already a lot of VMs in Azure?

Actually we only change the way to create storage account in the 0.7.0. We didn't change the ARM template. So I can't give you a clear reason why it happened now. But you can try to catch full ARM template in the deployment in portal. If there's something different, it may give me some hint.

henti@geekware.co.za (JIRA)

unread,
Apr 18, 2018, 10:25:02 AM4/18/18
to jenkinsc...@googlegroups.com

Chenyang Liu

 

I'm going to setup a test instance to test the upgrade separately. It might very well be an issue on the day at that time on azure that caused it. Will see and report back. 

henti@geekware.co.za (JIRA)

unread,
Apr 23, 2018, 7:52:02 AM4/23/18
to jenkinsc...@googlegroups.com

Chenyang Liu

After running succesfully on 1.6.2, this morning the problem started again. I've since tested manually deploying a VM using our image on the azure portal, which failed with the same message 

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"AllocationFailed\",\r\n \"message\": \"Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.\"\r\n }\r\n ]\r\n }\r\n}"}]}

This seems to indicate that it is an Azure problem. 

While this ticket was created for the failure, I think it's important this ticket now highlight the lack of infrastructure failure/error handling. 

Clearly there are error states that indicate that either the Azure infrastructure is not available or that capacity in a specific region has been reached leading to deployment failures. 

Can this please be addressed in the short term with at least race mitigation so that the plugin does not attempt and fail at deploying 300+ VMs in an hour. 

For the long term, please add support for multi region handling of agents to mitigate localised regional failures in Azure.  

chenyl@microsoft.com (JIRA)

unread,
Jun 28, 2018, 9:25:02 PM6/28/18
to jenkinsc...@googlegroups.com
Chenyang Liu resolved as Fixed
 
Change By: Chenyang Liu
Status: In Progress Resolved
Resolution: Fixed
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

chenyl@microsoft.com (JIRA)

unread,
Jun 28, 2018, 9:25:02 PM6/28/18
to jenkinsc...@googlegroups.com
Chenyang Liu commented on Bug JENKINS-50850
 
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0

In 0.7.1, the plugin has a longer retry interval if deployment failed. So it won't try to create a lot of deployments again.
Reply all
Reply to author
Forward
0 new messages