apache / apache/cloudstack

VLAN/VNI field not populated in GUI / Can't modify physical network

Open
#13,804 6 comments 0 reactions 0 assignees View on GitHub
bug component:UI type:regression
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

### problem

On a fresh install of 4.23 RC1, which has been updated to RC2, I have an advanced zone with two physical networks.

If we look here, you'll notice the GUI does not display VLAN/VNI ranges for the networks:

Image

If however, I go to the Zone and click Physical Networks, it is displayed:

Image

The additional oddity is if I click on either of the Physical Network and then select update, I get an empty dialog:

Image

cmk commands such as listPhysicalNetworks and updatePhysicalNetwork seem to work fine so this may be only cosmetic.

I also notice the following in the management server logs which may or may not be related:
```
2026-08-05 15:42:54,633 WARN [c.c.a.d.ParamGenericValidationWorker] (qtp1129944640-366:[ctx-4d3f4f4d, ctx-5aa8a355]) (logid:81214d13) Received unknown parameters for command listPhysicalNetworks. Unknown parameters :listall
2026-08-05 15:42:54,639 DEBUG [c.c.a.ApiServlet] (qtp1129944640-366:[ctx-4d3f4f4d, ctx-5aa8a355]) (logid:81214d13) ===END=== 192.168.197.203 -- GET listall=true&page=1&pagesize=20&command=listPhysicalNetworks&response=json&
```

### versions

4.23 RC2

### The steps to reproduce the bug

1. Install 4.23 RC2.
2. Create an advanced zone with multiple physical networks
3. Attempt to view or modify vlan/vni ranges associated with the physical networks.

### What to do about it?

Investigate further. It is unclear if this is specific to my install. I will attempt a re-build and other Physical Network structures to determine if this is a unique occurrence and perhaps narrow it down further.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the GUI requests and responses for the zone’s Physical Networks view with the listPhysicalNetworks and updatePhysicalNetwork commands, including the logged listall parameter. Trace how VLAN/VNI ranges are displayed and how the update dialog is populated. Done means the ranges appear in the network view and the update dialog contains the existing physical-network fields.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.