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

   > [!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
   
   When one node VM of a CKS cluster is not Running, the status scanner moves 
the cluster to `Alert`. `scaleKubernetesCluster` refuses every request in that 
state, including adding nodes and removing the broken node by `nodeids`, so the 
CloudStack cluster autoscaler is also blocked. The reporter identifies the 
missing `ScaleUpRequested` and `ScaleDownRequested` transitions from `Alert`, 
and two further blockers: the scale-up waits for all nodes to be Ready, and 
removal drains a NotReady node that cannot finish draining.
   
   ### ๐Ÿ“Š Assessment
   
   | Dimension | Value | Reasoning |
   | --- | --- | --- |
   | **Type** | type:bug | Recovery and autoscaling are refused in a state that 
should allow them |
   | **Component** | component:cks | CKS state machine and scale worker |
   | **Severity** | Severity:Major | A single stopped node blocks scaling and 
autoscaling |
   | **Labels** | type:bug, component:cks, Severity:Major |  |
   | **Coding agent** | Needs more info | Fix direction is given, but the 
change touches the state machine, scale worker and drain logic; maintainers 
should confirm the design |
   
   ### ๐Ÿ”— Similar issues
   
   - #14608 (related) โ€” concurrent CKS operations clobber state; same state 
machine area
   - #14610 (related) โ€” drain on scale-down and upgrade fails too easily
   - #14552 (related) โ€” scale requests without an offering resize nodes to an 
outdated offering
   
   <details>
   <summary>๐Ÿ’ก Notes and suggestions</summary>
   
   - Reproduction: a CKS cluster with two or more workers, stop one worker VM, 
then call `scaleKubernetesCluster` with a larger size and with `nodeids`.
   - Any change should keep offering and autoscaling changes refused in Alert, 
as the reporter suggests.
   
   </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]

Reply via email to