After the request, the status of Loadbalancer does not change from PENDING_UPDATE.
When checking the source code, there is no logic to check for duplicates.
In the controller logic(member.py), members are classified into new_members/updated_members/deleted_member, but the new_members data is being passed as is with duplicates, so this is suspected to be the cause of the problem.
By mistake, I sent wrong request with duplicated ip, port compbination through the Batch Update Members API. /docs.openstack .org/api- ref/load- balancer/ v2/#batch- update- members
https:/
For example :
"subnet_ id": "xxxxxxx",
"address" : "192.0.2.16",
"protocol_ port": 80
"subnet_ id": "xxxxxxx",
"address" : "192.0.2.16",
"protocol_ port": 80
{
"members": [
{
}, {
}
]
}
After the request, the status of Loadbalancer does not change from PENDING_UPDATE.
When checking the source code, there is no logic to check for duplicates.
In the controller logic(member.py), members are classified into new_members/ updated_ members/ deleted_ member, but the new_members data is being passed as is with duplicates, so this is suspected to be the cause of the problem.