la-wu opened a new issue, #14524: URL: https://github.com/apache/cloudstack/issues/14524
### problem We are unable to create an instance with a compute offering that has a linked disk offering with a custom disk size. We get the error: Request failed. (431) This disk offering requires a custom size specified This happens if the compute offering is the first one in the list. And therefor is automatically selected when starting the deployment wizard. If the first compute offering is without a link disk offering there is no problem. Also once switching to an compute offering without linked disk offering and back fixes the issue. Or once enable and disable the override root disk size toggle fixes the issue. You can see in the right column that the disk size for the new VM is missing without one of the workarounds. In the logs you can see that api call is without disk size parameter. > command=deployVirtualMachine > response=json > zoneid=09925517-9585-4086-af6e-effbb33aab96 > boottype=BIOS > bootmode=LEGACY > dynamicscalingenabled=true > iothreadsenabled=false > templateid=1ccdbe7f-7171-49c5-8138-94fa1ea5444b > startvm=false > serviceofferingid=3f530db6-dddc-4b73-be1a-38c45a0eea81 > details[0].cpuNumber=1 > details[0].memory=1024 > overridediskofferingid=3c634fa6-1f90-4987-b1bb-a3c79169df35 > affinitygroupids= > iptonetworklist[0].networkid=38ddac2d-28cd-4fc9-8e11-e03ccc65e3a9 > keypairs= > name=test > displayname=test > account=java-admins > domainid=63b3c0cc-f29e-4630-938a-aeb6f9ff35e9 > sessionkey=UKUQ9cFqocMPzmqNzA32amnEqTE I also faced the issue when I tried to deploy a Veeam worker using the Veeam Backup Integration. ### versions ACS: 4.23.0 MGMT Server OS: Rocky Linux 10.2 Hypervisor: KVM on Rocky Linux 10.2 Java: 21 ### The steps to reproduce the bug 1) Create a disk offering with "custom disk size" enabled 2) Create a compute offering with "Compute only disk offering" disabled and select the created disk Offering 3) Make sure the compute offering is the first one in the compute offering list 4) Create a new instance and just select the desired Account, Infrastructure and Name 5) The creation fails with: Request failed. (431) This disk offering requires a custom size specified ### What to do about it? The VM should be created with the root disk size from the template. Issue looks similar the same like: [issue:7115](https://github.com/apache/cloudstack/issues/7115) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
