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 <[email protected]> Date: Monday, July 8, 2024 at 9:19 PM To: [email protected] <[email protected]> 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.
