fix: SCALE_IN action not honoring specified node count
The SCALE_IN action in the lb_policy module was removing only
one node from the load balancer, regardless of the specified
count when the count was greater than 1. This was due to a
hard-coded count of 1 in the _get_delete_candidates function.
The root cause has been addressed by updating the
_get_delete_candidates function to dynamically handle the count
for SCALE_IN. The count is now retrieved from the action inputs,
and if not specified or invalid, it defaults to 1.
Reviewed: https:/ /review. opendev. org/c/openstack /senlin/ +/904800 /opendev. org/openstack/ senlin/ commit/ 2b6693576355b67 3dcc4e3e53f1291 204412c512
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 2b6693576355b67 3dcc4e3e53f1291 204412c512
Author: Nguyen Ngoc Hieu <email address hidden>
Date: Fri Jan 5 02:26:04 2024 +0700
fix: SCALE_IN action not honoring specified node count
The SCALE_IN action in the lb_policy module was removing only candidates function.
one node from the load balancer, regardless of the specified
count when the count was greater than 1. This was due to a
hard-coded count of 1 in the _get_delete_
The root cause has been addressed by updating the delete_ candidates function to dynamically handle the count
_get_
for SCALE_IN. The count is now retrieved from the action inputs,
and if not specified or invalid, it defaults to 1.
Closes-Bug: #2048099 58ef5ef84de8766 8e9668cec80
Change-Id: I9ff12dec26f4c5