[JIRA] (JENKINS-58961) Cannot provision vm because of 'specify OS disk size' issue

0 views
Skip to first unread message

olivier@vernin.me (JIRA)

unread,
Aug 16, 2019, 5:22:02 AM8/16/19
to jenkinsc...@googlegroups.com
Olivier Vernin created an issue
 
Jenkins / Bug JENKINS-58961
Cannot provision vm because of 'specify OS disk size' issue
Issue Type: Bug Bug
Assignee: Azure DevOps
Components: azure-vm-agents-plugin
Created: 2019-08-16 09:20
Environment: Jenkins 2.176.2
Priority: Critical Critical
Reporter: Olivier Vernin

Failure creating provisioned agent 'win201-2a84f12'
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:win201-2a84f12 - BadRequest - {error={code=BadRequest, message=Could not find member 'diskSizeGB' on object of type 'OSDisk'. Path 'properties.storageProfile.osDisk.diskSizeGB', line 1, position 670., target=vm.properties.storageProfile.osDisk.diskSizeGB}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:572)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:818)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:796)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

olivier@vernin.me (JIRA)

unread,
Aug 16, 2019, 5:51:02 AM8/16/19
to jenkinsc...@googlegroups.com
Olivier Vernin commented on Bug JENKINS-58961
 
Re: Cannot provision vm because of 'specify OS disk size' issue

If we keep the default value for 'OS disk size in GB (Optional)' which is 0, then provisionning work as expected

jieshe@microsoft.com (JIRA)

unread,
Aug 18, 2019, 10:58:02 PM8/18/19
to jenkinsc...@googlegroups.com
Jie Shen assigned an issue to Jie Shen
 
Change By: Jie Shen
Assignee: Azure DevOps Jie Shen

jieshe@microsoft.com (JIRA)

unread,
Aug 18, 2019, 11:00:01 PM8/18/19
to jenkinsc...@googlegroups.com
Jie Shen commented on Bug JENKINS-58961
 
Re: Cannot provision vm because of 'specify OS disk size' issue

Different image configuration need different different disk size setting. Need more investigation on how to set os disk size for this case.

rtyler@brokenco.de (JIRA)

unread,
Aug 19, 2019, 11:17:02 AM8/19/19
to jenkinsc...@googlegroups.com

Just to make sure this detail isn't lost. We did not see any issues here until we tried the "Pool" retention strategy (in effect, 0 size disk, with pool retention). We have reverted our configuration to a Idle retention strategy with the default "0" size disk.

jieshe@microsoft.com (JIRA)

unread,
Sep 2, 2019, 3:40:02 AM9/2/19
to jenkinsc...@googlegroups.com
Jie Shen commented on Bug JENKINS-58961

Instead of the retention strategy, I think this error is caused by the disks type setting. It seems that only Managed disk could support customized OS disk size.

Reply all
Reply to author
Forward
0 new messages