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:
If however, I go to the Zone and click Physical Networks, it is displayed:
The additional oddity is if I click on either of the Physical Network and then select update, I get an empty dialog:
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
- Install 4.23 RC2.
- Create an advanced zone with multiple physical networks
- 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.
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:
If however, I go to the Zone and click Physical Networks, it is displayed:
The additional oddity is if I click on either of the Physical Network and then select update, I get an empty dialog:
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:
versions
4.23 RC2
The steps to reproduce the bug
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.