Bug 2239179

Summary:	rhosp 16 octavia unable to specify port or weight for allocated members when creating an LB
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	python-django-horizon	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Ashish Gupta <ashigupt>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	gthiemon, rdopiera
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-19 15:16:04 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 David Hill 2023-09-15 18:15:19 UTC

What are you experiencing? What are you expecting to happen?
RHOSP 16.2.  Just recently updated to latest container images.  Now, when using horizon UI to create a load balancer in Chrome or Edge, when adding allocated members to the load balancer in the "Pool Members" area, there are no fields to specify port or weight.  Then the load balancer cannot be created because port is required.  We tested in Firefox, and the Port and Weight fields are present and modifiable.  This worked before the recent updates.

Current versions:
Horizon: 16.2.5-6
Octavia: 16.2.5-6

Define the value or impact to you or the business
Workaround exists with firefox, but inconvenience

It worked as expected with:
octavia - 16.2.4-16
horizon - 16.2.4-19

Comment 1 David Hill 2023-09-15 18:29:41 UTC

I suspect we miss this patch

commit 9cc4bfac58b901b32c58d36ffab3585645f79be5
Author: Gregory Thiemonge <gthiemon>
Date:   Fri Jun 16 08:22:10 2023 -0400

    Fix popover attributes in member add dialog
    
    Using popovers in the member table is broken in chrome 114, because of
    their new "popover" feature.
    
    Closes-Bug: #2024188
    Change-Id: Idb009295495c1d8c732e792a72d58912e0e8d3a7

Comment 3 Gregory Thiemonge 2023-09-19 15:16:04 UTC


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