github-actions[bot] commented on issue #14597: URL: https://github.com/apache/cloudstack/issues/14597#issuecomment-6744187504
> [!WARNING] > threat detection engine error > The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding. > > <!-- gh-aw-threat-engine-error --> > > <details> > <summary>What happened</summary> > > The threat detection engine failed to produce results. > > Review the [workflow run logs](https://github.com/apache/cloudstack/actions/runs/42625769126) for details. > > </details> ## 🎯 Triage report Three CKS add-on scripts mishandle downloads. `deploy-csi-driver` never fetches `manifest.yaml` when the binaries ISO lacks CSI manifests, so enabling the CSI driver fails. `deploy-provider` and `autoscale-kube-cluster` use `curl -sSL` without `-f`, so HTTP error pages can be saved and applied as manifests. `autoscale-kube-cluster --disable` is also rejected because the option is declared as `-d | --enable)`. The reporter provides exact error messages and line-level causes. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | Scripts fail or apply bad files, with reproduction steps | | **Component** | component:cks | Scripts in `plugins/integrations/kubernetes-service` | | **Severity** | Severity:Major | CSI enablement always fails on ISOs without CSI manifests; bad files persist under `/opt` | | **Labels** | type:bug, component:cks, Severity:Major | | | **Coding agent** | Suitable | Specific fixes listed: download all CSI files before apply, use `curl -f`, accept `--disable`, use `--ignore-not-found` | ### 🔗 Similar issues - #14244 (related) — CKS upgrade fails when the binaries ISO ships a different dashboard manifest - #11596 (related) — CKS cluster does not come up with an experimental feature setting <details> <summary>💡 Notes and suggestions</summary> - Reproduction is in the report: a CKS control node whose ISO lacks `/opt/csi/*.yaml`, then `deploy-csi-driver`. - The issue applies to both 4.22 and main, per the reporter. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/42625769126) · copilot · haiku55 · \~4 AIC · ⊞ 3.8K · [◷](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) <details> <summary><sub>Add this agentic workflow to your repo</sub></summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@139fa09ef17cde4135e696ff8e7af09bc5ddfa6e ``` </details> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, model: claude-haiku-5.5, id: 42625769126, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/42625769126 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"42625769126","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/42625769126","publishing_job":{"key":"safe_outputs","check_run_id":"129262122857"}} --> -- 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]
