[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy For provisioning more nodes than the limits, it is an existing issue JENKINS-56972 caused by bad concurrency control. I will try to fix this later. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198672.1554998321000.23114.1557468720092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy di wang I have tested with vnet configuration(delete and provision several times), but I still get no luck to reproduce your error. I use the latest version on the dev branch for the configuration as code work done on the branch and it is should be a stable one with some fixes. And below is my configuration: - azureVM: azureCredentialsId: "imds" cloudName: "jsdev" configurationStatus: "pass" deploymentTimeout: 1200 existingResourceGroupName: "Testing" maxVirtualMachinesLimit: 10 newResourceGroupName: "jieshe-dev-agents" resourceGroupReferenceType: "new" vmTemplates: - agentLaunchMethod: "SSH" availabilityType: availabilitySet: "avset" builtInImage: "Windows Server 2016" credentialsId: "agent_admin_account" diskType: "managed" doNotUseMachineIfInitFails: true enableMSI: false executeInitScriptAsRoot: true existingStorageAccountName: "fsxvergehbetgzsvfg" imageReference: offer: "UbuntuServer" publisher: "Canonical" sku: "16.04-LTS" version: "latest" imageTopLevelType: "advanced" initScript: "sudo add-apt-repository ppa:openjdk-r/ppa -y\nsudo apt-get -y\ \ update\nsudo apt-get install openjdk-8-jre openjdk-8-jre-headless openjdk-8-jdk\ \ -y" installDocker: false installGit: false installMaven: false labels: "advanced" location: "East US" newStorageAccountName: "asdfwefwef" noOfParallelJobs: 1 osDiskSize: 0 osType: "Linux" preInstallSsh: true retentionStrategy: azureVMCloudPool: poolSize: 1 retentionInHours: 24 shutdownOnIdle: false storageAccountNameReferenceType: "new" storageAccountType: "Standard_LRS" subnetName: "jenkins" templateDisabled: false templateName: "advanced" usageMode: "Use this node as much as possible" usePrivateIP: true virtualMachineSize: "Standard_F2s" virtualNetworkName: "jenkins-vnet" virtualNetworkResourceGroupName: "jieshe-jenkins" Do I miss anything in the configuration that make me unable to reproduce the error on my side? Add Comment
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie, do we have a fix for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198672.1554998321000.22142.1557411420701%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie, do we have a fix for this? [~jieshe] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198672.1554998321000.22144.1557411421177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.50.40 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy With more testing, I config the max vm nunmber is 4 which the pool size is 1. I submit a branch of requests to trigger it. As it thinks test-vm407940 was failed, then it provisioned another 4 vm. So total is 5 now, more than the max vm number I configured. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Oops, please ignore my last comment. Even the same error appears, but the vm provisioned successfully this time. I saw it in the jenkins agent list. However, Cloud Statistics report it failed and no further report of it(test-vm407940), like "Operation time" and etc. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title
di wang edited a comment on JENKINS-56981
Re: VM failed to provision when use Pool Retention Strategy
Built a snapshot plugin based on [https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515]Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. The latest provision failed but no more attempts after it. Check attached new pic. {quote}Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test-vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test-vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk.jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins-testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test-vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels=packerApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMCloud$3 callINFO: Azure Cloud: provision: Adding agent test-vm407940 to Jenkins nodesApr 30, 2019 4:18:51 PM
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title
di wang edited a comment on JENKINS-56981
Re: VM failed to provision when use Pool Retention Strategy
Built a snapshot plugin based on [https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515]Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. Check attached new pic. {quote}Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test- vmApr vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test- vm40794Apr vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk. jsonApr jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins- testApr testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test- vm407940Apr vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels= packerApr packerApr 30, 2019 4:18:51 PM
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Built a snapshot plugin based on https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515 Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded. It is the same error. See new attached pic. From jenkins log, it looks like it thinks it provisioned successfully, but it actually didn't. Check attached new pic. Apr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Initializing deployment for agentTemplate test-vmApr 30, 2019 4:17:09 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Creating a new deployment test-vm0430161709407 with VM base name test-vm40794Apr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeploymentINFO: AzureVMManagementServiceDelegate: createDeployment: Use embedded deployment template (with managed) /referenceImageIDTemplateWithManagedDisk.jsonApr 30, 2019 4:17:10 PM com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar registerDeploymentINFO: AzureVMAgentCleanUpTask: registerDeployment: Registering deployment test-vm0430161709407 in cardinal-jenkins-testApr 30, 2019 4:17:13 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment test-vm0430161709407 to be completedApr 30, 2019 4:17:43 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 90fe5df5-b8e3-403c-b4c8-5ad1e8b43a32] Instance discovery was successfulApr 30, 2019 4:17:43 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:07 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: Deployment test-vm0430161709407 not yet finished (Running): Microsoft.Compute/virtualMachines:test-vm407940 - waited 30 secondsApr 30, 2019 4:18:37 PM com.microsoft.aad.adal4j.AuthenticationAuthority doInstanceDiscoveryINFO: [Correlation ID: 22087788-162d-4386-b453-f33292ef2516] Instance discovery was successfulApr 30, 2019 4:18:38 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Apr 30, 2019 4:18:48 PM com.microsoft.azure.vmagent.AzureVMCloud createProvisionedAgentINFO: AzureVMCloud: createProvisionedAgent: VM available: test-vm407940Apr 30, 2019 4:18:49 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate parseResponseINFO: AzureVMManagementServiceDelegate: parseDeploymentResponse: found agent test-vm407940 OS type Linux number of executors 1Apr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: The Azure agent doesn't have a public IP. Will use the private IPApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate setVirtualMachineDetailsINFO: Azure agent details:nodeNametest-vm407940adminUserName=azure-jenkinsshutdownOnIdle=falseretentionTimeInMin=0labels=packerApr 30, 2019 4:18:51 PM com.microsoft.azure.vmagent.AzureVMCloud$3 callINFO: Azure Cloud: provision: Adding agent test-vm407940 to
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.31.45 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.24.13 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: Screen Shot 2019-04-30 at 4.20.06 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy [~diwang] are you able to build a SNAP-SHOOT SNAPSHOT version with the above PR checked in? If so, please verify it in your Jenkins. If not, you can install the 0.7.5 ([https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/azure-vm-agents/0.7.5/]) version which does not contain the bug. Instruction at [https://jenkins.io/doc/book/managing/plugins/#advanced-installation] . The ProvisioningActivity error log seems to only affect cloud statics, so it will not prevent provisioning VMs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy di wang are you able to build a SNAP-SHOOT version with the above PR checked in? If so, please verify it in your Jenkins. If not, you can install the 0.7.5 (https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/azure-vm-agents/0.7.5/) version which does not contain the bug. Instruction at https://jenkins.io/doc/book/managing/plugins/#advanced-installation . The ProvisioningActivity error log seems to only affect cloud statics, so it will not prevent provisioning VMs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Are you able to reproduce the issue? Do you need any other information? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy I have made a PR to fix one bug for pool retention strategy. But the your issue seems not related with it. I am afraid the advanced configuration parameters caused the provisioned agents into improper status. And this leads the clean up task to delete them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie Shen do you have any update on this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Even though I can use pool retention strategy to provision an agent and successfully run a job. But its behavior is not what I excepted. It cannot maintain a healthy pool of agents for my further jobs. Need more investigation on this strategy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy attached the errors that I just tried today. As mentioned Observe it for an hour now. It looks like it created VM first, but shut it down after 1 or 2 minutes. I don't know why it shut the new VM down as it suppose to keep the new VM to maintain the pool. Maybe because of above error? Anyway , eventually no VMs can be created after switch to pool retention strategy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy attached the errors that I just tried today. As mentioned above, no VMs can be created after switch to pool retention strategy. !pic7.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title
di wang edited a comment on JENKINS-56981
Re: VM failed to provision when use Pool Retention Strategy
The VM can not be created when use pool retention strategy as you can see in pic1. All of them failed with the same error as posted in the ticket above. I also attached my settings pic2 to pic5. With this setting("idle retention strategy" in pic3), all VMs can created successfully triggered by label "m1". However, if I change retention strategy to "pool retention strategy" (pic6), then it starts failed to create VMs. Please let me know if you need any additional data, or please suggest any instructions on how to troubleshoot. !pic1.png!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang edited a comment on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy attached new the errors that I just tried today. As mentioned above, no VMs can be created after switch to pool retention strategy. !pic7.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: pic7.png Attachment: pic8.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy attached new errors that I just tried today. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title
di wang commented on JENKINS-56981
Re: VM failed to provision when use Pool Retention Strategy
The VM can not be created when use pool retention strategy as you can see in pic1. All of them failed with the same error as posted in the ticket above. I also attached my settings pic2 to pic5. With this setting("idle retention strategy" in pic3), all VMs can created successfully triggered by label "m1". However, if I change retention strategy to "pool retention strategy" (pic6), then it starts failed to create VMs. Please let me know if you need any additional data, or please suggest any instructions on how to troubleshoot.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang updated an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: di wang Attachment: pic1.png Attachment: pic2.png Attachment: pic3.png Attachment: pic4.png Attachment: pic5.png Attachment: pic6.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Hi di wang, do you mean no VM could be created successfully with your settings? I just check it in my environment, it seems to work well for me. Your log is just for clean up action, could you please provide the reason for its failed deployment? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Azure DevOps assigned an issue to Jie Shen Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: Azure DevOps Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Azure DevOps started work on JENKINS-56981 Change By: Azure DevOps Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang created an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-04-11 15:58 Environment: Jenkins 2.150.1 Azure VM Agents 0.9.0 [root@pkrvmv9zkwan3x3 centos]# cat /etc/*release CentOS Linux release 7.6.1810 (Core) NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" CentOS Linux release 7.6.1810 (Core) CentOS Linux release 7.6.1810 (Core) Priority: Major Reporter: di wang When use pool retention strategy, most times VMs are failed to provision. If use the same template settings, only change retention strategy to Idle retention strategy, then all vms can provisioned successfully(100%). Retention time in hour: 24 Pool Size: 1 Only a few times, VMs can be provisioned successfully with pool retention strategy. Node ProvisioningActivity for Azure-Test/jenkins-… java.lang.Exception: Node ProvisioningActivity for Azure-Test/jenkins-test/null (229415501) has lost. Mark as failure at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanCloudStatistics(AzureVMAgentCleanUpTask.java:604) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.clean(AzureVMAgentCleanUpTask.java:622) at
