github-actions[bot] commented on issue #14571: URL: https://github.com/apache/cloudstack/issues/14571#issuecomment-6632284213
> [!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/41838428837) for details. > > </details> ## 🎯 Triage report An admin asks for a way to order guest networks, as is already possible for ISOs, templates, and offerings, so the top network is the default in the UI instead of the last one added. This is a feature request, not a bug. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:enhancement | Feature request for ordering behaviour | | **Component** | component:UI | Network selection order is visible in the UI | | **Severity** | n/a | Not a bug report | | **Labels** | type:enhancement, component:UI | Based only on the issue text | | **Coding agent** | Needs more info | Unclear whether ordering is stored per account, domain, or zone, and whether the API needs a sort field | ### 🔗 Similar issues - #14573 (related) — UI: add additional NICs (guest networks) that belong to the same project - #12941 (related, closed) — guest network created on the wrong physical network <details> <summary>💡 Notes and suggestions</summary> - Maintainers should decide where the order is stored (per account, per domain, or global) and whether it is an API change or UI-only. - Compare with how the existing ordering works for offerings in the UI. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/41838428837) · copilot · haiku55 · \~2 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: 41838428837, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/41838428837 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"41838428837","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/41838428837","publishing_job":{"key":"safe_outputs","check_run_id":"126611980414"}} --> -- 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]
