[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy

[jie...@microsoft.com (JIRA)]

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   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.23112.1557468300099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.