Repository navigation
Unable to orchestrate start VM instance on fresh 4.20 #10091
Description
I had a 4.18.x installation that worked perfectly with Linstor. VMs were created without any issues, and everything functioned flawlessly. Since this was a test environment, I decided to upgrade to 4.20. The upgrade completed successfully, with no errors encountered.
However, when I attempted to create a VM, I encountered the following error:
Unable to orchestrate start VM instance.
I assumed there might be an issue in the integration with Linstor, so I decided to perform a clean installation of 4.20. The installation went smoothly, and the configuration and settings were identical to those in 4.18. Despite this, VMs still fail to create.
When creating a VM, I see the following in the logs:
2024-12-11 17:11:19,788 DEBUG [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-85:[ctx-9a91bf59, job-975/job-976, ctx-e5509a97]) (logid:01094d38) Cleaning up resources for the vm VM instance {"id":267,"instanceName":"i-2-267
-VM","type":"User","uuid":"aea7fd99-a309-4599-9003-facbca54a849"} in Starting state
2024-12-11 17:11:19,801 DEBUG [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-85:[ctx-9a91bf59, job-975/job-976, ctx-e5509a97]) (logid:01094d38) VM instance {"id":267,"instanceName":"i-2-267-VM","type":"User","uuid":"aea7fd
99-a309-4599-9003-facbca54a849"} is a [User], returning null for control Nic IP.
Then the status changes:
2024-12-11 17:11:20,234 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-85:[ctx-9a91bf59, job-975/job-976, ctx-e5509a97]) (logid:01094d38) VM instance {"id":267,"instanceName":"i-2-267-VM","type":"User","uuid":"aea7fd99-a309-4599-90
03-facbca54a849"} state transited from [Starting] to [Stopped] with event [OperationFailed]. VM's original host: null, new host: null, host before state transition: Host {"id":2,"name":"cloud-node02","type":"Routing","uuid":"f8b0e878-2f8
2-490c-9dd1-2ba5f2dea128"}
It feels like the issue might be network-related:
2024-12-11 17:11:20,275 ERROR [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-85:[ctx-9a91bf59, job-975/job-976, ctx-e5509a97]) (logid:01094d38) Unable to orchestrate start VM instance {"id":267,"instanceName":"i-2-267-VM",
"type":"User","uuid":"aea7fd99-a309-4599-9003-facbca54a849"} due to [Failed to implement network id=206 as a part preparing nic id=765]
The installation was performed on AlmaLinux 9.5.
I checked the network settings, and everything appears to be in order.
Activity
weizhouapache commentedon Dec 12, 2024
can you share the full log of job job-975 ?
happyalexkg commentedon Dec 12, 2024
job-1058.txt
Hi,
I have already cleaned the log. Here is the log from the repeated VM creation attempt .Logs attached
weizhouapache commentedon Dec 12, 2024
the log file shows
2024-12-12 14:06:05,685 ERROR [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-127:[ctx-cf554c81, job-1058/job-1059, ctx-c3a2aead]) (logid:82bc6300) Caught exception: No suitable host found for vm [VM instance {"id":276,"instanceName":"r-276-VM","type":"DomainRouter","uuid":"7fd53f56-7297-4077-b121-5b2ea53659ad"}].slavkap commentedon Dec 12, 2024
@happyalexkg, from what I see the offering (probably that for the router) has a Host tag but the host itself doesn't
that's why it fails with the error that there are no suitable hosts
happyalexkg commentedon Dec 12, 2024
Computer offering
Host 1
Host 2
Instance
both host and offerings having correct tags and router offering also
Router
happyalexkg commentedon Dec 12, 2024
Hi,
I removed Storage tag for Software Router and seems, it's works now :)
Thank you for you support
Big Thanks
slavkap commentedon Dec 12, 2024
@happyalexkg, I'm unfamiliar with the host's tags and the new functionality introduced for them. But from what I saw in the code you need to set the host tag as a Rule for the host when you use it with offerings. Probably @weizhouapache could correct me if I'm wrong
happyalexkg commentedon Dec 12, 2024
yes, host tags was in offerings and hosts... but seems issue was in storage tag in Router Offering
Removing Storage Tag resolves issue with creating VM