Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2295157

Summary: [OSP17.1] using google chrome the loadbalancer pool, the weight and port number do not display
Product: Red Hat OpenStack Reporter: Ricardo Ramos Thomas <riramos>
Component: openstack-octavia-uiAssignee: Nate Johnston <njohnston>
Status: CLOSED DUPLICATE QA Contact: Bruna Bonguardo <bbonguar>
Severity: high Docs Contact: Greg Rakauskas <gregraka>
Priority: unspecified    
Version: 17.1 (Wallaby)CC: gthiemon, tweining
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-09 07:11:47 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 Ricardo Ramos Thomas 2024-07-02 11:35:56 UTC 
Description of problem:

The Load Balancer was successfully created and the Operating Status and Provisioning Status is "active". However, i cant add members to the pool via Horizon. The "Add Pool Members" button is not working. Most probably because you have to enter the Port for each member, which is mandatory but i cant enter the ports either (See Screenshot)

Adding the members with CLI is working as intended.


Using Google Chrome and MS Edge, not able to enter the port of the added pool members. But with Firefox works.

Looks like was reported upstream:

https://bugs.launchpad.net/octavia/+bug/2024188


Version-Release number of selected component (if applicable):

RHOSP 17.1 (wallaby)

How reproducible:

Using Horizon from Chrome or Edge web browser 

Steps to Reproduce:
1.Open octavia ui from Chrome or Edge web browser
2.
3.

Actual results:


Expected results:


Additional info:


- SOS reports and Screenshots available on the case
Comment 4 Gregory Thiemonge 2024-07-09 07:11:47 UTC 

*** This bug has been marked as a duplicate of bug 2215969 ***