Create Instance menu show empty values for offerings

[ManuFe]

Hello,

I've successfully installed CloudStack 4.20 and registered my first host. I can see it in the hosts session with the green flag for the Resource state column.

And I can see all the default offerings, for example:

But when I try to create a new instance I've got no offering selectable for any of the options:

It seems like all the api requests return blank. Instead the zone, pod, cluster and host settings are correctly shown and I can select them all if I want.

This is done with the default admin account created at the start.

The main error I see in the log is about this:
javax.net.ssl.SSLPeerUnverifiedException: Certificate for <10.0.0.1> doesn't match any of the subject alternative names: [XXXX] because I started installing CloudStack management host with other network settings then changed the ip address for the ethernet card to 10.0.0.1 and the "host" setting in global configuration with the UI.

Don't know if can be of any use. How can I fix this?

Got any solution for this kind of error?

Thank you.

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[DaanHoogland]

@ManuFe , did you install cmk (cloudmonkey)?
It would be interesting to know if the server backend is up and running. I do not think the certificate error is anything to worry about right now.
Are your systemVMs started?

[JoaoJandre]

@ManuFe Two questions that might help here:

1. Have you seeded the first system VM template?
2. Is your zone enabled?

[ManuFe]

Hello @JoaoJandre

I followed the guide for the CloudStack Management and Agent at Management Server Installation and Hypervisor KVM Configuration in two different machines so for point number one I am not able to answer. I'm pretty new to the CloudStack world.

For second point I see this:

As you can see is enabled. Cluster and pod are green too.

I've started with an edge zone, don't know if it's a problem, but I guess it should'nt be, at least to select the offerings from the wizard ui for the instance creation.

This is what I see in the wizard:

I can even select the host and in the dropdown menu the host I've configured appears.

I cannot just see any of the offerings for compute, disk, template

[JoaoJandre]

@ManuFe If you have followed the guides you linked, then you should've seeded the template already, it was the Prepare the System VM Template step.

I have never worked with edge zones, your problem may be there. @DaanHoogland @rohityadavcloud do you know if edge zones require further configuration to operate?

[ManuFe]

@JoaoJandre
I've executed the command and in fact I can do this:

sudo ls /export/secondary/template/tmpl/1/3
cb4be099-49d9-4584-8e27-4de987e16d3a.qcow2  template.properties

I executed the command for KVM
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /export/secondary -u http://download.cloudstack.org/systemvm/4.20/systemvmtemplate-4.20.0.0-x86_64-kvm.qcow2.bz2 -h kvm -F

but without the management server key optional parameter.

Moreover I can see it in the template images on the UI with the green dot.
It could be maybe the secondary storage configuration the problem?

I've got this now:

After I've added this the status for the system vm template turned green.

[ManuFe]

@JoaoJandre
In the Zone documentation there is written that "To work with limited compute resources, an Edge zone will not deploy system VMs."

That's why I cannot see any system VM up and running.

[shwstppr]

@ManuFe if you're working with edge zones, please keep in mind that to deploy an instance in it you would need,

• Direct-download templates
• Compute/disk offerings with local storage

You may refer https://www.shapeblue.com/edge-zones-feature-deep-dive/ for some additional details

[ManuFe]

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:

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:

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!

[shwstppr]

@ManuFe InsufficientServerCapacityException is very vague in identifying the real reason for the failure. More logs would be needed.
Your primary store looks okay so it might not be the problem here.
In edge zones, you don't need a secondary storage or NFS shared storage as a primary storage.
Please check:

• The templates are registered with direc-download flag
• The offering is created with Local storage option
• Host is showing as Up
  If nothing works then please share the logs for VM deployment so that I or someone else can help you find the issue.

[ManuFe]

Hello @shwstppr,

Yes to all the questions because otherwise in the create instance menu i would not able to see anything as you pointed out in the first answer.

Host is up with unsecure state, reachable and power state disabled.

The screenshot of the host is at the start of the thread.

The logs you need are both from management server and agent logs?

The .err and the .log?

Thank you

[shwstppr]

@ManuFe share management-server.log first. Try to share only relevant part - from the start of VM deployment

[ManuFe]

Hello @shwstppr

This is the host:

Host stats:

This is the image:

This is the compute offering:

In management-server.err this is the only thing repeated but I don't think it means anything for this issue:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Attached the last parts of the log, filtered for job-168 and job-170 that is the job it started while deploying a new instance.
job-168.log
job-170.log

One thing I see that can be the real issue is

INFO  [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-2:[ctx-221b02fe, job-168/job-170, ctx-64a2b573]) (logid:f6474b93) Unable to start VM on Host {"id":1,"name":"PC-XB09397","type":"Routing","uuid":"53aa0077-1d9f-4b36-a8b8-9019d92a3dc9"} due to internal error: process exited while connecting to monitor: 2025-02-22T11:03:23.991480Z qemu-system-x86_64: Cannot load CA certificate '/etc/pki/libvirt-vnc/ca-cert.pem': Error while reading file.

Thank you for the help.

[shwstppr]

@ManuFe your error looks similar to #9984
What OS are you using on your host?

[ManuFe]

@shwstppr Ubuntu 24.04 Desktop. They are two identical computers too hardware side. On both host and management

[ManuFe]

@shwstppr do you think that with a previous version, like Ubuntu 20.04/22.04, does it work?

Otherwise which host where you using in the video demonstration?

Thank you

[shwstppr]

@ManuFe yes, maybe try 22.04 for your host. In the demo I was using an el8 distro either Rocky Linux 8 or Alma Linux 8. Can't remember exactly.

[ManuFe]

@shwstppr no luck either with 22.04. Got a "Cannot find the server resources at http..." error and services are up and running correctly. I've done the same as in 24.04 configuration side.

I've seen there is an issue about that #9019 but on AlmaLinux

It seems like I won't be able to run any test. Bit of lost because I've done the commands as in the documentation for the agent configuration but couldn't make it work.

Guess I should do one last try with either Rocky Linux or Alma Linux.

[JoaoJandre]

Hi, @ManuFe

If you are going to try to redeploy a new environment, I would highly recommend using a core advanced zone, without security groups enabled. This is a more "default" setup that most people tend to use, and thus more people might be able to help you troubleshoot it.