Managed to test the case on 4.17.2. The issue does not seem to be present anymore!
Best regards, Jordan On Sun, Nov 13, 2022 at 12:26 PM jordan j <[email protected]> wrote: > I am on it, but it will take some time due to the conference next week. > > Regards, > Jordan > > On Wed, Nov 9, 2022 at 7:21 AM Harikrishna Patnala < > [email protected]> wrote: > >> Hi Jordan, >> >> From the deployVirtualMachine API body it seems like rootdisksize param >> is missing. Since overridediskofferingid: >> c7d11a8d-29eb-44b0-811c-fb57dbaac2a5 is a custom disk offering, >> rootdisksize should be there in the API params. Not sure about the root >> cause because I cannot reproduce this. >> >> If it is possible, can you please try on a completely new 4.17.1 setup, >> just to check if some problem upgrading the UI components ? >> >> Thanks, >> Harikrishna >> >> >> From: jordan j <[email protected]> >> Date: Tuesday, 8 November 2022 at 2:14 PM >> To: [email protected] <[email protected]> >> Subject: Re: compute cannot be used if rot disk size is 0 >> Good Morning Harikrishna, >> >> Fixed service offering with custom disk. During the GUI Instance creation >> I >> type 50 in the Root disk space box. >> >> >> 1. command: >> deployVirtualMachine >> 2. response: >> json >> 1. Form Dataview sourceview URL-encoded >> 1. zoneid: >> d4f93f7c-4236-475d-9968-765af32768b3 >> 2. boottype: >> BIOS >> 3. bootmode: >> LEGACY >> 4. templateid: >> d6e26141-0e03-41c9-b265-dd765a08a18b >> 5. startvm: >> true >> 6. serviceofferingid: >> 72a39b48-fb28-4588-bf57-0822ca107838 >> 7. overridediskofferingid: >> c7d11a8d-29eb-44b0-811c-fb57dbaac2a5 >> 8. affinitygroupids: >> 9. iptonetworklist[0].networkid: >> ac3c9873-2526-45c5-8fdc-d838104c6390 >> 10. keypairs: >> >> Request fails with error: >> >> 1. cserrorcode: 4350 >> 2. errorcode: 431 >> 3. errortext: "VM Creation failed. Volume size: -1GB is out of allowed >> range. Max: 1024 Min:1" >> 4. uuidList: [] >> >> >> >> >> >> On Mon, Nov 7, 2022 at 8:31 PM jordan j <[email protected]> wrote: >> >> > Disregard my last email. >> > I will hold the tests tomorrow and provide data. >> > >> > Regards, >> > Jordan >> > >> > On Mon, Nov 7, 2022 at 10:56 AM jordan j <[email protected]> wrote: >> > >> >> Harikrishna, >> >> >> >> Tried to reproduce today but it seems there is some new issue, probably >> >> caused by the upgrade from 4.17.0.1 to 4.17.1 i did last week. >> >> >> >> VMs cannot start as Domain VIrtual router initialization fails. >> >> What happens is: >> >> - a VM instance is launched (through the gui) >> >> - domain VR (r-393) is started, i can see it on the hypervisor that it >> >> fully boots but in ACS it is still shown as "Starting" >> >> - at some point the domain VR VM is halted and destroyed and the error >> >> below is produced in Cloudstack logs >> >> >> >> I have not done any changes to the system VM template. Can this be the >> >> issue? >> >> >> >> >> >> 2022-11-07 09:26:24,461 ERROR [c.c.v.VirtualMachineManagerImpl] >> >> (Work-Job-Executor-35:ctx-1b0a6cad job-3785/job-3786 ctx-cd97ffb5) >> >> (logid:e2508811) Failed to start instance VM instance {id: "393", name: >> >> "r-393-VM", uuid: "3d3637d5-afd9-4c5d-b5f8-a871460f6856", >> >> type="DomainRouter"} >> >> ....... >> >> 2022-11-07 09:26:24,586 ERROR [c.c.v.VmWorkJobDispatcher] >> >> (Work-Job-Executor-35:ctx-1b0a6cad job-3785/job-3786) (logid:e2508811) >> >> Unable to complete AsyncJobVO: {id:3786, userId: 2, accountId: 2, >> >> instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStart, >> >> cmdInfo: >> >> >> rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAACAAAAAAAAAAIAAAAAAAABiXQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAHBwcHBwcHBwc3IAEWphdmEudXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2FkRmFjdG9ySQAJdGhyZXNob2xkeHA_QAAAAAAADHcIAAAAEAAAAAF0AA5SZXN0YXJ0TmV0d29ya3QAP3JPMEFCWE55QUJGcVlYWmhMbXhoYm1jdVFtOXZiR1ZoYnMwZ2NvRFZuUHJ1QWdBQldnQUZkbUZzZFdWNGNBRXhw, >> >> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, >> >> result: null, initMsid: 99751975598799, completeMsid: null, >> lastUpdated: >> >> null, lastPolled: null, created: Mon Nov 07 09:24:49 CET 2022, removed: >> >> null}, job origin:3785 >> >> com.cloud.utils.exception.ExecutionException: Unable to start >> >> VM:3d3637d5-afd9-4c5d-b5f8-a871460f6856 due to error in >> finalizeStart, not >> >> retrying >> >> com.cloud.exception.AgentUnavailableException: Resource [Host:76] is >> >> unreachable: Host 76: Unable to start instance due to Unable to start >> >> VM:3d3637d5-afd9-4c5d-b5f8-a871460f6856 due to error in >> finalizeStart, not >> >> retrying >> >> ......... >> >> 2022-11-07 09:26:24,645 ERROR [c.c.a.ApiAsyncJobDispatcher] >> >> (API-Job-Executor-16:ctx-095e19bc job-3785) (logid:e2508811) Unexpected >> >> exception while executing >> >> org.apache.cloudstack.api.command.admin.router.StartRouterCmd >> >> com.cloud.exception.AgentUnavailableException: Resource [Host:76] is >> >> unreachable: Host 76: Unable to start instance due to Unable to start >> >> VM:3d3637d5-afd9-4c5d-b5f8-a871460f6856 due to error in >> finalizeStart, not >> >> retrying >> >> >> >> >> >> On Mon, Nov 7, 2022 at 5:18 AM Harikrishna Patnala < >> >> [email protected]> wrote: >> >> >> >>> Hi Jordan, >> >>> >> >>> I’ve tried the same cloudmonkey commands and it worked fine on my >> >>> environment. I don’t think the way we save the details in the >> database has >> >>> changed, not sure what is happening from UI front. >> >>> >> >>> Can you open the developers tools in the browser and capture the >> >>> “deployVirtualMachine” API request params and send us, so that I can >> verify >> >>> with my environment. >> >>> >> >>> Regards, >> >>> Harikrishna >> >>> >> >>> From: jordan j <[email protected]> >> >>> Date: Friday, 4 November 2022 at 2:01 PM >> >>> To: [email protected] <[email protected]> >> >>> Subject: Re: compute cannot be used if rot disk size is 0 >> >>> Yes CPU/RAM are fixed! >> >>> >> >>> Code for disk and service offering: >> >>> >> >>> createDiskOffering isMirrored=false name=custom-disk >> >>> displaytext=custom-disk storageType=local cacheMode=none >> >>> provisioningType=thin customized=true disksizestrictness=false >> >>> { >> >>> "diskoffering": { >> >>> "cacheMode": "none", >> >>> "created": "2022-11-04T09:27:03+0100", >> >>> "disksize": 0, >> >>> "disksizestrictness": false, >> >>> "displayoffering": true, >> >>> "displaytext": "custom-disk", >> >>> "hasannotations": false, >> >>> "id": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5", >> >>> "iscustomized": true, >> >>> "name": "custom-disk", >> >>> "provisioningtype": "thin", >> >>> "storagetype": "local" >> >>> } >> >>> } >> >>> >> >>> createServiceOffering issystem=false name=fixed-compute >> >>> displaytext=fixed-compute customized=false offerha=false >> >>> limitcpuuse=false >> >>> dynamicscalingenabled=true cpunumber=2 cpuspeed=2000 memory=2048 >> >>> diskofferingid=c7d11a8d-29eb-44b0-811c-fb57dbaac2a5 >> >>> { >> >>> "serviceoffering": { >> >>> "cacheMode": "none", >> >>> "cpunumber": 2, >> >>> "cpuspeed": 2000, >> >>> "created": "2022-11-04T09:28:52+0100", >> >>> "defaultuse": false, >> >>> "diskofferingdisplaytext": "custom-disk", >> >>> "diskofferingid": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5", >> >>> "diskofferingname": "custom-disk", >> >>> "diskofferingstrictness": false, >> >>> "displaytext": "fixed-compute", >> >>> "dynamicscalingenabled": true, >> >>> "hasannotations": false, >> >>> "id": "f5a61b2f-9b03-4322-9d10-bb69033a87dd", >> >>> "iscustomized": false, >> >>> "issystem": false, >> >>> "isvolatile": false, >> >>> "limitcpuuse": false, >> >>> "memory": 2048, >> >>> "name": "fixed-compute", >> >>> "offerha": false, >> >>> "provisioningtype": "thin", >> >>> "rootdisksize": 0, >> >>> "storagetype": "local" >> >>> } >> >>> } >> >>> >> >>> Regards, >> >>> Jordan >> >>> >> >>> On Fri, Nov 4, 2022 at 3:22 AM Harikrishna Patnala < >> >>> [email protected]> wrote: >> >>> >> >>> > Can you please share the CLI list responses of the service offering >> and >> >>> > disk offering (fixed-compute-with-custom-disk) that you have used in >> >>> your >> >>> > case 2, so that I’ll create the exact same offerings and try to >> deploy >> >>> the >> >>> > VM. >> >>> > >> >>> > When you say “Create any service offering (used fixed for the >> test)”, >> >>> do >> >>> > you mean fixed compute details like CPU, RAM ? >> >>> > >> >>> > Thanks, >> >>> > Harikrishna >> >>> > >> >>> > From: jordan j <[email protected]> >> >>> > Date: Thursday, 3 November 2022 at 2:06 PM >> >>> > To: [email protected] <[email protected]> >> >>> > Subject: Re: compute cannot be used if rot disk size is 0 >> >>> > Hi Harikrishna! >> >>> > >> >>> > Upgraded to 4.17.1 and did some more tests. >> >>> > >> >>> > 1. Create any service offering mapped to disk offering with fixed >> size >> >>> - >> >>> > this works >> >>> > 2. Create any service offering (used fixed for the test) mapped to >> disk >> >>> > offering with custom size - this brings the error mentioned during >> >>> instance >> >>> > creation. >> >>> > >> >>> > During case 2 when in GUI there is Root disk size (GB) option but >> it >> >>> does >> >>> > not matter to what it is set, the error always appears. >> >>> > This case is similar to what you do in case 3. The question is what >> is >> >>> it >> >>> > that you do that makes it work on your side and fail on mine. >> >>> > >> >>> > Here is a link with the error message and the options selected >> during >> >>> > instance creation: https://imgur.com/l3WktFg >> >>> > DIsk offering is custom and I set it to 50 but ACS does not take it >> >>> into >> >>> > account and still thinks it is 0. >> >>> > >> >>> > Regards, >> >>> > Jordan >> >>> > >> >>> > On Thu, Nov 3, 2022 at 9:26 AM Harikrishna Patnala < >> >>> > [email protected]> wrote: >> >>> > >> >>> > > Hi Jordan, >> >>> > > >> >>> > > I’ve tried these scenarios in 4.17.1 and it seems to be working >> fine. >> >>> > This >> >>> > > might be an issue in 4.17 but it is working fine in 4.17.1 >> >>> > > >> >>> > > I tried the following scenarios, >> >>> > > >> >>> > > 1. Created a service offering with an existing disk offering >> and >> >>> > > deployed VM with it from GUI. It worked fine. >> >>> > > 2. Tried the same from CLI (without rootdisksize). It worked >> fine. >> >>> > > 3. Created a service offering with an existing CUSTOM disk >> >>> offering >> >>> > and >> >>> > > deployed VM with it from GUI. It worked fine too. >> >>> > > >> >>> > > Can you please try upgrading your environment to 4.17.1 ? >> >>> > > >> >>> > > Also I did not understand your scenario why rootdisksize comes to >> >>> picture >> >>> > > when diskoffering is mapped to a service offering ? Is that a >> custom >> >>> disk >> >>> > > offering ? >> >>> > > >> >>> > > Thanks, >> >>> > > Harikrishna >> >>> > > From: jordan j <[email protected]> >> >>> > > Date: Wednesday, 2 November 2022 at 8:01 PM >> >>> > > To: [email protected] <[email protected]> >> >>> > > Subject: compute cannot be used if rot disk size is 0 >> >>> > > Hey everyone, >> >>> > > >> >>> > > I found a bug (4.17.0.1). >> >>> > > >> >>> > > if you try to create an instance from compute offering that has >> root >> >>> disk >> >>> > > size = 0 the following error appears: >> >>> > > VM Creation failed. Volume size: -1GB is out of allowed range. >> Max: >> >>> 1024 >> >>> > > Min:1 >> >>> > > >> >>> > > A few examples when rootdisk size is set as 0: >> >>> > > - when compute offering is created and matched to existing disk >> >>> offering >> >>> > > >> >>> > > --> via GUI same thing as CLI >> >>> > > If a compute offering is created by specifying existing disk >> >>> offering, >> >>> > > the root disk size is set as 0 >> >>> > > Workaround: When creating Compute offering, enable "Compute only >> disk >> >>> > > offering" option, change the root disk size to a value larger >> than 0. >> >>> > After >> >>> > > that disable "Compute only disk offering" and attach to existing >> disk >> >>> > > offering. >> >>> > > >> >>> > > --> via CLI - in the example below the rootdisk is defined as 10 >> but >> >>> it >> >>> > > will not be set as diskofferringid overrides it. So 0 will be the >> end >> >>> > > result. >> >>> > > create serviceoffering name=infra-compute >> displaytext=infra-compute >> >>> > > customized=true dynamicscalingenabled=true cpuspeed=2000 >> >>> mincpunumber=1 >> >>> > > maxcpunumber=4 minmemory=512 maxmemory=2048 >> >>> > > diskofferingid=851dd105-77ee-45d9-8094-807c9824a053 >> rootdisksize=10 >> >>> > > >> >>> > > Is there any workaround for cli on how to update the rootdisksize >> ? >> >>> > > update serviceoffering does not allow such modification. >> >>> > > >> >>> > > Regards, >> >>> > > Jordan >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> >> >>> >> >>> >> >>> >> >
