[I] Add Network: no way to disable Isolated/Shared + "Request failed" on those tabs [cloudstack]

["nabassa1323 (via GitHub)" <gi...@apache.org>]

nabassa1323 opened a new issue, #14377:
URL: https://github.com/apache/cloudstack/issues/14377

   ### The required feature described as a wish
   
   Hi,
   
   On CloudStack 4.22.1.0 (modern UI), Guest Networks → Add Network always shows Isolated, L2 and Shared tabs.
   
   Context
   We only want to allow L2 networks. We disabled all Isolated and Shared network offerings (only L2 offerings remain Enabled). L2 correctly lists offerings; Isolated/Shared have no usable offering. The tabs still remain visible — there seems to be no global setting/option to hide them.
   
   UI issue
   When opening Add Network, the Isolated and Shared tabs trigger "Request failed" (while L2 works). With offerings disabled, the UI should not fail like this: an empty list or a clear message would be better. Ideally there would also be a way to hide/disable those network guest types.
   
   Questions / requests
   
   Is there a supported way to disable or hide Isolated and Shared in Add Network?
   If not: feature request to restrict available guest types (e.g. L2 only).
   Is "Request failed" on Isolated/Shared when no offering is available a known UI/API bug?
   
   Thanks


-- 
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: commits-unsubscribe@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add Network: no way to disable Isolated/Shared + "Request failed" on those tabs [cloudstack]

["nabassa1323 (via GitHub)" <gi...@apache.org>]

nabassa1323 commented on issue #14377:
URL: https://github.com/apache/cloudstack/issues/14377#issuecomment-6164274495

   Opened PR https://github.com/apache/cloudstack/pull/14399 for the UI empty-state / "Request failed" fix.
   Hiding unused guest-type tabs can be a follow-up enhancement.


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add Network: no way to disable Isolated/Shared + "Request failed" on those tabs [cloudstack]

["DaanHoogland (via GitHub)" <gi...@apache.org>]

DaanHoogland commented on issue #14377:
URL: https://github.com/apache/cloudstack/issues/14377#issuecomment-6267894124

   @nabassa1323 , can you rebase your changes in #14399 to branch 4.22?


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Add Network: no way to disable Isolated/Shared + "Request failed" on those tabs [cloudstack]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

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

   ## 🎯 Triage report
   
   On CloudStack 4.22.1.0 (modern UI), the Guest Networks → Add Network dialog always shows Isolated/L2/Shared tabs regardless of whether any enabled network offerings exist for those guest types. Selecting Isolated or Shared (which have no enabled offerings in this environment) results in a "Request failed" error instead of a graceful empty state, and there is no setting to hide unused guest types.
   
   ### 📊 Assessment
   
   | Dimension | Value | Reasoning |
   |---|---|---|
   | **Type** | `type:bug` | The "Request failed" error on tabs with no available offerings is unexpected/unhandled UI behavior rather than a deliberate design; the request to hide guest types is a secondary enhancement ask. |
   | **Component** | `component:UI`, `component:networking` | Issue is in the Add Network dialog of the modern UI, related to network offering/guest type handling. |
   | **Severity** | `Severity:Minor` | Workaround exists (use the working L2 tab); no data loss or system outage, just a confusing error and missing UX polish. |
   | **Labels** | type:bug, component:UI, component:networking, Severity:Minor | See above. |
   | **Coding agent** | Needs more info | The error-handling bug (graceful empty state instead of "Request failed") could be fixed with reproduction via browser dev tools/network tab to see the failing API call, but the broader ask (global setting to hide guest types) is a design decision requiring maintainer input. |
   
   ### 🔗 Similar issues
   
   No similar open issues were found in a search for related "Add Network", offering-related UI failures.
   
   <details><summary>💡 Notes and suggestions</summary>
   
   - To reproduce/debug: open browser dev tools → Network tab while clicking the Isolated/Shared tabs in Add Network with no enabled offerings for those guest types, and capture the failing API call (likely `listNetworkOfferings` or similar) and its response/error.
   - Two distinct asks bundled in this issue: (1) bug — UI should handle "no offerings available" gracefully (empty state/message) instead of "Request failed"; (2) feature request — admin-configurable setting to hide/restrict guest network types shown in Add Network.
   - Maintainers may want to split this into a bug fix (UI error handling) and a separate feature request (restrict guest types), since they have different scope and priority.
   
   </details>
   
   
   
   > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/38259167693) · sonnet50 93.6K · [◷](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues)
   >
   <details>
   <summary>Add this agentic workflows to your repo</summary>
   
   To install this agentic workflow, run
   
   ```
   gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9
   ```
   </details>
   
   
   <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 38259167693, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/38259167693 -->
   <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage -->


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org