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

   > [!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
   
   Two CKS state problems. First, `KubernetesClusterDaoImpl.updateState` writes 
by id without checking the current state, so two operations started together 
(for example a scale and an upgrade) can both proceed. Second, if the 
management server running an operation stops partway, the cluster stays in that 
operation's transient state, and the scanner's handling of `Starting` clusters 
tries a transition that does not exist. The reporter proposes compare-and-set 
updates, moving to the operation's state before any change, and having the 
scanner fail operations that have no job running.
   
   ### ๐Ÿ“Š Assessment
   
   | Dimension | Value | Reasoning |
   | --- | --- | --- |
   | **Type** | type:bug | Race condition and stuck state after restart, with 
reproduction steps |
   | **Component** | component:cks | CKS cluster state DAO, workers and status 
scanner |
   | **Severity** | Severity:Major | Clusters can become stuck and only be 
fixed by editing the DB |
   | **Labels** | type:bug, component:cks, Severity:Major |  |
   | **Coding agent** | Not suitable | Cross-cutting state-machine and 
concurrency change needing maintainer design |
   
   ### ๐Ÿ”— Similar issues
   
   - #14603 (related) โ€” CKS cluster in Alert cannot be scaled
   - #14610 (related) โ€” failed upgrade cannot be resumed
   - #14213 (related) โ€” CKS nodes report stale capacity after live resize
   
   <details>
   <summary>๐Ÿ’ก Notes and suggestions</summary>
   
   - The `TODO: ensure this update is correct` in `updateState` is the place to 
start.
   - Reproduction for the race: call `scaleKubernetesCluster` and 
`upgradeKubernetesCluster` on a running cluster at the same time.
   
   </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