github-actions[bot] commented on issue #12816: URL: https://github.com/apache/cloudstack/issues/12816#issuecomment-5294166994
## ๐ฏ Triage report Adding NFS primary storage to a Proxmox-orchestrator-backed cluster fails with `"Missing required fields: url user token secret node"` from the bundled `proxmox.sh` extension script, even after removing an incorrectly-required `vm_internal_name` field. This blocks primary storage from reaching "Up", which in turn prevents any VM deployment on Proxmox-backed hosts. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Extension script validation logic appears to reject valid `createStoragePool` requests; connectivity/auth to Proxmox was independently verified as working | | **Component** | component:primary-storage, component:plugin | Built-in Proxmox orchestrator extension (`proxmox.sh`) and primary storage add flow | | **Severity** | Severity:Major | Completely blocks primary storage and therefore all VM deployment for Proxmox-backed clusters | | **Labels** | type:bug, component:primary-storage, component:plugin, Severity:Major | | | **Coding agent** | Not suitable | Requires investigation into how `createStoragePool` payload/`externaldetails` are passed to the extension script, and possibly a design decision on the extension's field-validation approach | ### ๐ Similar issues - https://github.com/apache/cloudstack/issues/12239 (related) โ "Unable to acquire Additional Disks/volume for Proxmox VMs โ Primary Storage Not Available" describes the downstream symptom of primary storage being unavailable for Proxmox, likely the same root cause. - https://github.com/apache/cloudstack/issues/12363 (related) โ "Encountered issues when attempting to bootstrap CloudStack with Proxmox" โ broader Proxmox integration issues that may share root cause. <details><summary>๐ก Notes and suggestions</summary> - Reporter already did useful triage themselves: patched `check_required_fields` to remove `vm_internal_name` from the global validation in `parse_json()`, but the error persisted โ suggesting the `createStoragePool` payload itself may not include `externaldetails.host`/`externaldetails.extension` data as expected. - Suggested next step: inspect the Java-side code that builds the `CreateStoragePool` extension command payload (likely in the Proxmox orchestrator plugin) to confirm host/extension config fields are actually populated before being passed to the shell script. - Given the overlap with #12239 and #12363, consider consolidating investigation across all three Proxmox extension issues. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/31806898936) ยท sonnet50 357.5K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 31806898936, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/31806898936 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
