Real Problem After the Cloud Stack Upgrade

[kirankumar034]

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

[boring-cyborg[bot]]

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

[DaanHoogland]

@kirankumar034 , please add your from - and to versions .

[DaanHoogland]

and a description of the scenario in which you encountered this please

[DaanHoogland]

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]

@kirankumar034
can you provider more details ?

[github-actions[bot]]

🎯 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

Dimension	Value	Reasoning
Type	type:question	Insufficient detail to confirm this is a bug; could be a misunderstanding of error propagation/anonymization behavior
Component	none	Cannot confirm affected component without from/to versions and scenario details
Severity	n/a	Cannot assess without reproduction details
Labels	type:question
Coding agent	Not suitable	No reproduction steps, versions, or scenario details provided; not actionable as-is

🔗 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.

Generated by Daily Issue Triage · sonnet50 259.3K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9

[MugdhoAI]

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.