Bug 2043914

Summary: provisioning_status is not changed according to API reference when member weight is set to 0
Product: Red Hat OpenStack Reporter: Alex Stupnikov <astupnik>
Component: openstack-octaviaAssignee: Tom Weininger <tweining>
Status: CLOSED ERRATA QA Contact: Bruna Bonguardo <bbonguar>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: beagles, ihrachys, lpeer, majopela, scohen
Target Milestone: z3Keywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-octavia-ui-4.0.3-2.20220309025520.12ca23a.el8ost openstack-octavia-5.1.3-2.20220309165023.052c864.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-22 16:03:23 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 Alex Stupnikov 2022-01-22 12:46:03 UTC
Description of problem:

One of our customers reported cosmetic Octavia problem: member operating_status is not set to DRAINING when its weight is 0. I checked the code introduced in change [1] and it looks like Octavia should change member's operating status accordingly in such cases.

Outputs from customer's deployment would be provided privately.

[1]
https://review.opendev.org/c/openstack/octavia/+/487671

Comment 5 Tom Weininger 2022-03-10 08:54:56 UTC
In addition to fixing this issue in Octavia itself, I also adjusted the dashboard, because even if a member was in DRAINING state the dashboard did not show it.

Comment 12 errata-xmlrpc 2022-06-22 16:03:23 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 (Release of components for Red Hat OpenStack Platform 16.2.3 (Train)), 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-2022:4793