Bug 2269001

Summary: port names display blank records port list (in horizon only)
Product: Red Hat OpenStack Reporter: John Soliman <jsoliman>
Component: python-django-horizonAssignee: Tatiana Ovchinnikova <tovchinn>
Status: CLOSED ERRATA QA Contact: Ashish Gupta <ashigupt>
Severity: low Docs Contact:
Priority: urgent    
Version: 17.1 (Wallaby)CC: bcafarel, dalvarez, dsedgmen, jinjli, jjasek, jjoyce, jpretori, jschluet, ltamagno, mariel, pgrist, rdopiera, rhos-maint, slinaber, tovchinn, tpass, tvignaud, xili
Target Milestone: z4Keywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-19.4.1-17.1.20240606150803.9b1a13e.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-21 09:39:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Soliman 2024-03-11 13:03:16 UTC
Description of problem:
In the Horizon dashboard when clicking the "Create Instance" button for the first time in the interface, the port names and IPs in the port list are blank (the records exist but do not show the port names and IPs), then After clicking the "Create Instance" button for the second time, the port name in the port list can be displayed normally.
This problem exists in any project, including admin user.

Troubleshooting Done:

- restarted tripleo_horizon.service, then tripleo_memcached service, and neutron on three controller nodes. the issue still exists.
- tried to reproduce on CU environment using other browsers (chrome/firefox) still exists.
- change the port name without using "-", Issue still exists

- Note: OSP CLI works normally, only related to horizon 

from browser logs, there are some errors noticed:

(anonymous) @ output.76da13f1b5e5.js:1382
(anonymous) @ output.76da13f1b5e5.js:1243

------

output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'subnet_names')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'name')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'subnet_names')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'name')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'subnet_names')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'name')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'subnet_names')
output.76da13f1b5e5.js:1382 TypeError: Cannot read properties of undefined (reading 'name')

Version-Release number of selected component (if applicable):
RHOSP 17.1.2
puppet-horizon-18.6.1-17.1.20230621075748.8074e69.el9ost.noarch
python3-django-horizon-19.4.1-17.1.20230621085933.9b1a13e.el9ost.noarch

How reproducible:
100% can be reproduced at will 

Steps to Reproduce:
in CU env:
1. Use Chrome/firefox as a web browser (cache already cleaned)
2. click the "reload" button 
3. click the "create instance" button.
4. check the port list, many ports cannot be found 
5. close the "create instance" tab
6. click the "create instance" button again, all ports can be observed

Tested on RHOSP 17.1 lab but did not face the cu issue
executed following steps as admin user under admin project.
 - create test_net
 - create test_subnet
 - create test_port within above test_net  
test_port is available in the create vm step in Horizon regardless network is shared or not.

Actual results:
clicking the "Create Instance" button for the first time in the interface, the port names and IPs in the port list are blank (the records exist but do not show the port names and IPs)

Expected results:
clicking the "Create Instance" button for the first time shows records of ports and IPs

Additional info:
sos-reports from controllers attached to the case.

Comment 31 errata-xmlrpc 2024-11-21 09:39:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHOSP 17.1.4 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2024:9974