github-actions[bot] commented on issue #14628:
URL: https://github.com/apache/cloudstack/issues/14628#issuecomment-6769044248

   > [!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
   
   A CKS cluster created before 4.21 cannot be scaled up after upgrading to 
4.21 or later. The per-node-type template columns added in 4.21 are NULL for 
these clusters, so node VM creation receives a null template and throws an NPE. 
The reporter has a DB workaround (set the control and worker template IDs to 
the cluster's `template_id`) and proposes falling back to the default CKS 
template in code.
   
   ### 📊 Assessment
   
   | Dimension | Value | Reasoning |
   | --- | --- | --- |
   | **Type** | type:bug | NPE on scale-up for clusters created before 4.21 |
   | **Component** | component:cks | CKS node provisioning |
   | **Severity** | Severity:Major | Scale-up of upgraded clusters fails; a DB 
workaround exists |
   | **Labels** | type:bug, component:cks, Severity:Major |  |
   | **Coding agent** | Suitable | Cause and fix direction are specific: fall 
back to the default template and treat it as default for launch permission |
   
   ### 🔗 Similar issues
   
   - #14504 (related) — CKS control and worker node service offerings are not 
populated
   - #14458 (related) — `nodeids` scale-in can resize unrelated nodes to the 
legacy cluster offering
   
   <details>
   <summary>💡 Notes and suggestions</summary>
   
   - Reproduction: create a CKS cluster on 4.20, upgrade to 4.21 or later, then 
scale up by one worker.
   - Check `isDefaultTemplateUsed()` as well, since the report says the 
launch-permission logic is affected too.
   
   </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]

Reply via email to