github-actions[bot] commented on issue #14630: URL: https://github.com/apache/cloudstack/issues/14630#issuecomment-6769043426
> [!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/42824790094) for details. > > </details> ## 🎯 Triage report On main, a CKS upgrade, scale-up or start fails immediately if a node VM already has an ISO attached, for example the binaries ISO left by an operation that did not finish. Since #13101, `attachIso` refuses an ISO that is already attached. With the default one-CD-ROM limit it also refuses any second ISO. 4.22 is not affected. A fix is already open as #14637. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | Regression on main from the CD-ROM limit change (#13101) | | **Component** | component:cks | `KubernetesClusterActionWorker.attachIsoKubernetesVMs` | | **Severity** | Severity:Major | Blocks upgrade, scale and start until ISOs are detached by hand | | **Labels** | type:bug, component:cks, Severity:Major | | | **Coding agent** | Suitable | Fix is specified, and PR #14637 is already open for review | ### 🔗 Similar issues - #14608 (related) — concurrent CKS operations and interrupted operations leave the cluster in a bad state; an interrupted operation is how the ISO is left behind <details> <summary>💡 Notes and suggestions</summary> - Reproduction: attach the cluster's binaries ISO to a node VM, then upgrade or scale the cluster. - Check the start path as well, since the report says start also fails. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/42824790094) · copilot · haiku55 · \~5 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: 42824790094, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/42824790094 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"42824790094","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/42824790094","publishing_job":{"key":"safe_outputs","check_run_id":"129867538613"}} --> -- 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]
