Hi Marty, Can you check and ensure all your CloudStack hosts (management server, kvm hosts if applicable and ssvm, cpvm) are on the same version (4.19.0.2) & restarted post update/upgrade.
Once you've done this, can you share your management server logs where you see the exceptions/errors around VM deployment. You may also want to check if you've any capacity issues, or using any offering that's tagged (host or storage tags) for which you don't have available capacity? Regards. ________________________________ From: Marty Godsey <mar...@rudio.net> Sent: Tuesday, July 9, 2024 07:29 To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: Unable to create new VMs or Console Proxy Ok, figured, out the service offerings issues, I rebooted the database and it came back. I still can not create VMs. It is stating that the storage is suitable, but it is in avoid set. I have no idea why it is in avoid set since all hosts and the Cloudstack management server can get to it. Where would I check this? From: Marty Godsey <mar...@rudio.net> Date: Monday, July 8, 2024 at 9:19 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Unable to create new VMs or Console Proxy WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Question. All of a sudden, I cannot create new VMs, and the console proxy also can’t be created. As I spent the past hour looking, I have found that in the console, when I go to offerings for compute, disk, or system, I get a 404, and it says it can’t find anything for domain -1. But when I look in the database, I see the offerings. I took this opportunity to update to 4.19.0.2 since I was already on 4.19.0.1. At first I thought it was storage but it is not. Running VMS and secStorage and VRs are all running fine. Where should I look from here? Nothing was changed for the root domain.
