Comment 0 for bug 2067441

By mistake, I sent wrong request with duplicated ip, port compbination through the Batch Update Members API.
https://docs.openstack.org/api-ref/load-balancer/v2/#batch-update-members

For example :
{
    "members": [
        {
            "subnet_id": "xxxxxxx",
            "address": "192.0.2.16",
            "protocol_port": 80
        }, {
            "subnet_id": "xxxxxxx",
            "address": "192.0.2.16",
            "protocol_port": 80
        }
    ]
}

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.