github-actions[bot] commented on issue #10517: URL: https://github.com/apache/cloudstack/issues/10517#issuecomment-6520628424
> [!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/41040764159) for details. > > </details> ## 🎯 Triage report The SSVM fails to start when S3 is configured as image store. The management server throws an NPE in `SecondaryStorageManagerImpl.addSecondaryStorageServerAddressToBuffer` because the image store's `url` is null. The reporter also sees the S3 store with no `url` in `list imagestores` output, and browsing the store fails with "No remote endpoint to send command". A maintainer commented in March 2025 that S3 secondary storage has not had proper maintenance, and a later comment reports the issue still present on 4.22.0. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | Stack trace shows an NPE on a null URL during SSVM start | | **Component** | component:secondary-storage | SSVM startup and image store browsing | | **Severity** | Severity:Major | SSVM cannot start with S3 secondary storage; S3 may be unsupported in practice | | **Labels** | type:bug, component:secondary-storage, Severity:Major | | | **Coding agent** | Needs more info | Root cause of the null URL on S3 stores is not established; S3 maintenance status is a maintainer question | ### 🔗 Similar issues - #9002 (related) — default systemVM template not downloaded to S3 secondary storage; same S3 store area - #13774 (related) — SSVM cannot mount secondary storage on isolated storage network <details> <summary>💡 Notes and suggestions</summary> - Maintainers should confirm whether S3 secondary storage is still a supported configuration, as the March 2025 comment suggests. - Check how `url` is populated for S3 image stores on add. The `list imagestores` output in the report shows only `name`. - Reproduce by adding an S3 image store and checking the SSVM start path. The NPE is at `SecondaryStorageManagerImpl.java:1228` per the reporter's stack trace. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/41040764159) · copilot · haiku55 · \~3 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: 41040764159, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/41040764159 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"41040764159","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/41040764159","publishing_job":{"key":"safe_outputs","check_run_id":"124016161242"}} --> -- 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]
