github-actions[bot] commented on issue #14704: URL: https://github.com/apache/cloudstack/issues/14704#issuecomment-6918569386
> [!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/43879158606) for details. > > </details> ## ๐ฏ Triage report On a default KVM install, a running CKS cluster cannot be scaled live. The KVM SystemVM template is registered with `dynamically_scalable = 0`, so CKS nodes built from it are not dynamically scalable, and a live offering change fails with "does not have tools to support dynamic scaling". The reporter proposes registering KVM SystemVM templates as dynamically scalable, both for new registrations and through the upgrade SQL for existing ones. PR #14705 is already open for this. ### ๐ Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | The documented live offering change does not work on a default install | | **Component** | component:cks, component:kvm | CKS node scaling, and the KVM SystemVM template flag | | **Severity** | Severity:Minor | Blocked by default; a manual template change works around it, and no data loss is reported | | **Labels** | type:bug, component:cks, component:kvm, Severity:Minor | Based on the issue text | | **Coding agent** | Needs more info | The fix is specified and PR #14705 exists, but the system VM question below needs a maintainer decision | ### ๐ Similar issues - #13226 (related, closed) โ enabled live scaling of CKS offerings on KVM; this issue covers the default-install case that the change does not reach - #14615 (related) โ changes CKS node offerings and root disks through a rolling restart - #14213 (related) โ CKS nodes report stale capacity after a live resize <details> <summary>๐ก Notes and suggestions</summary> - Reproduction: on a KVM zone with `enable.dynamic.scale.vm=true`, create a CKS cluster with the default node template, then change its service offering while it is running. - The upgrade SQL has to cover every existing KVM SystemVM template row, because the template-registration change runs too late for the new row. - Existing CKS nodes keep their old flag until they are recreated. The report asks for this to be stated in the release notes and CKS docs. - Open question for maintainers: routers, SSVM and console proxy copy the template flag and ignore their offering's dynamic-scaling setting. The reporter asks whether this was deliberate. Making system VMs scalable also reduces usable memory by about 67 MB on small system VMs, which the report measures. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/43879158606) ยท copilot ยท haiku55 ยท \~6 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: 43879158606, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/43879158606 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"43879158606","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/43879158606","publishing_job":{"key":"safe_outputs","check_run_id":"133346438628"}} --> -- 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]
