Repository navigation
Real Problem After the Cloud Stack Upgrade #13072
Description
problem
Before the upgrade, CloudStack was surfacing this error clearly in the UI:
"No more available PCI slots"
After the upgrade, CloudStack swallows the error from the KVM agent and only shows:
"null job execution result"
This is a CloudStack bug introduced in the upgrade — the error propagation from agent → management server → UI is broken.
versions
The versions of ACS, hypervisors, storage, network etc..
The steps to reproduce the bug
...
What to do about it?
No response
Activity
boring-cyborg commentedon Apr 27, 2026
Thanks for opening your first issue here! Be sure to follow the issue template!
DaanHoogland commentedon Apr 28, 2026
@kirankumar034 , please add your from - and to versions .
DaanHoogland commentedon Apr 28, 2026
and a description of the scenario in which you encountered this please
DaanHoogland commentedon Apr 29, 2026
also @kirankumar034 , can you specify which accounts/roles face this? some messages have been anonymised for non-privileged users lately. This may be a result of that.
weizhouapache commentedon May 8, 2026
@kirankumar034
can you provider more details ?
github-actions commentedon Aug 18, 2026
🎯 Triage report
Reporter claims that after a CloudStack upgrade, a previously clear error ("No more available PCI slots" from the KVM agent) is now replaced by a generic "null job execution result" message, suggesting broken error propagation from agent to UI. However, the report is missing versions, reproduction steps, and other required details — maintainers have asked twice for more information with no response yet.
📊 Assessment
🔗 Similar issues
No similar open issues found via search.
💡 Notes and suggestions
Maintainers (DaanHoogland, weizhouapache) have already asked twice for the from/to CloudStack versions, the exact scenario, and affected account/role, since some error messages may be intentionally anonymized for non-privileged users. Recommend closing/downgrading priority if no response is received after a reasonable follow-up window.
Add this agentic workflows to your repo
To install this agentic workflow, run