GitHub user ManuFe added a comment to the discussion: Create Instance menu show 
empty values for offerings

Hello @shwstppr 

Thank you for the template. It seems like you were right because I've got this 
in the management server log:
```
ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-2:[ctx-e16fa298, 
job-111]) (logid:a7ab0f49) Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin 
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
[852f6080-63e6-46fd-8822-bd77c1e6bba4] due to [Unable to create a deployment 
for VM instance 
{"id":5,"instanceName":"i-2-5-VM","type":"User","uuid":"852f6080-63e6-46fd-8822-bd77c1e6bba4"}].
Caused by: com.cloud.exception.InsufficientServerCapacityException:
```

This is the instance:
![image](https://github.com/user-attachments/assets/dfbc353b-5f9c-4111-9aab-04275f4e3862)

I don't get how it's possible. I've used no disk offering, just compute 
offering, but even with disk offering no luck. Anyway the local storage has 250 
free GB:
![image](https://github.com/user-attachments/assets/911d76ae-b044-4ab2-a8a5-91e49f9ff225)

Since it's registered as NFS I guess the problem could reside there. 

This primary storage auto added itself after I setted the UUID value for local 
storage in the agent.properties file.
I see in your video that the path is the same for the host you added in zone 
creation phase.
Secondary storage is up from the management server and I can mount it on host.

Moreover if I disable the primary storage the message is different since it 
says that no volumes was found for that. 

Even exporting that dir in /etc/exports with then exportfs -a command did not 
change anything.

Sorry If I bother you but it seems pretty strange!

GitHub link: 
https://github.com/apache/cloudstack/discussions/10421#discussioncomment-12267341

----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Reply via email to