Hello Eugen, Perhaps you are looking for [1] that was fixed in 23.3.0 (2023.2 Bobcat) Best regards Tobias [1] https://launchpad.net/openstack/horizon/+bug/2020630
On 15 Apr 2025, at 14:11, Eugen Block <eblock@nde.ag> wrote:
Hi *,
I've been searching for an existing bug report but haven't found one yet.
OpenStack Zed (Antelope 2023.1 is also affected) openstack-dashboard versions 23.0.0 and also 23.2.0
Both environments have been upgraded from Victoria relatively quick, that's why we haven't noticed it until now, but apparently there have been major workflow changes between Victoria and Wallaby how network ports are displayed in Horizon (Launch Instance).
When we open the "Launch Instance" dialog in Horizon, and we want to attach an existing port (created via CLI) to the instance, only some of the ports in the list are displayed with a name, many don't have one, although all ports were created with a name via CLI (it would have failed without providing a name).
A colleague of mine helped debugging and he suspects a JavaScript error, I'm translating his statement:
Some sort of cache is built, coming from an array which is supposed to store all relevant ports. Apparently, not all ports have been stored yet in that array in time, leading to this inconsistency. If there's a missing "async" or "await" somewhere, it would explain this behavior.
He then points to these functions: getPortsObj, isPortsObjGenerated which are called by getNameOrId. I found those calls here:
/usr/lib/python3/dist-packages/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/networkports/ports.controller.js
and here
/usr/lib/python3/dist-packages/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/networkports/ports.spec.js
Is anyone aware of an existing bug report for this? I can create one, if necessary.
Thanks! Eugen