GitHub user MugdhoAI added a comment to the discussion: Real Problem After the Cloud Stack Upgrade
I think there are two things worth separating here. "No more available PCI slots" looks like the underlying KVM/libvirt error, while "null job execution result" looks like what is being exposed after the upgrade. I would first compare the exact CloudStack versions before and after the upgrade, then check the KVM agent and management server logs for the same operation. It would also be useful to try the operation with an administrator account and the affected account. DaanHoogland mentioned that some error messages have recently been anonymised for non privileged users. If the administrator sees the original error while the affected account gets "null job execution result", that would help confirm whether this is related to error anonymisation. If the original error reaches the management server but disappears from the API or UI response, then the error handling around the async job result would be the next place to investigate. The exact from/to versions, the operation that triggers the error, and the affected account or role would help narrow this down. GitHub link: https://github.com/apache/cloudstack/discussions/13918#discussioncomment-18699983 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
