Add Network: no way to disable Isolated/Shared + "Request failed" on those tabs #14377

Activity

1. github-actions

   added

   component:networking

   component:UI

   Severity:Minor

   type:bug

   on Oct 12, 2026
2. github-actions commented on Oct 12, 2026

   

   github-actionsbot

   on Oct 12, 2026 – with GitHub Actions

   More actions

   🎯 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.

   💡 Notes and suggestions

   • 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.

   Generated by Daily Issue Triage · sonnet50 93.6K · ◷

   Add this agentic workflows to your repo

   To install this agentic workflow, run

   gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9