github-actions[bot] commented on issue #14629: URL: https://github.com/apache/cloudstack/issues/14629#issuecomment-6769044683
> [!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 After a CKS upgrade, each upgraded node's Kubernetes version is stored as raw `kubectl` output, so it includes a leading `v` and a trailing newline (for example `v1.33.1\n`). Nodes added by create or scale store `1.33.1`. Clients that print the field see a stray line break, and the two forms do not compare equal. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | Stored data format is inconsistent between upgrade and create/scale | | **Component** | component:cks | Upgrade worker and `KubernetesClusterUtil` | | **Severity** | Severity:Minor | Mostly cosmetic in API output, but comparisons break | | **Labels** | type:bug, component:cks, Severity:Minor | | | **Coding agent** | Suitable | Fix is specified: record the target version, not the command output | ### 🔗 Similar issues - #14610 (related) — CKS upgrade and drain failures in the same upgrade worker <details> <summary>💡 Notes and suggestions</summary> - Reproduction: upgrade a CKS cluster, then check `kubernetesnodeversion` in `listKubernetesClusters`, or `kubernetes_node_version` in `kubernetes_cluster_vm_map`. - The report also notes that stderr from the SSH command (for example a `sudo` warning) can end up in the same field. </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]
