[neutron-lbaas] neutron-lbaasv2-agent not updating the Member status based on collected haproxy stats

[sajuptpm]

In neutron-lbaasv2-agent code, I could not find the statements which updating the Member status based on collected haproxy stats.I could find same logic in neutron-lbaas-agent code.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/334676

[Armando Migliaccio (armando-migliaccio)]

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Yang Zhang (bjzyang)]

Hello, this bug is also affecting me. Here is my testing result for your reference:

1. I have a working load balancer with 2 members, port 80 enabled with round-robin policy;
2. I stopped the VM for one of the member, the load balancer can still work well, all traffic could be routed to another member VM (I can recognize that according to the specific response from the web server);
3. But if I check the status of the load balancer by CLI command "neutron lbaas-loadbalancer-status <lb_name>", it was still showing "provisioning_status": "ACTIVE", "operating_status": "ONLINE".

Please help clarify whether this is as design or it's a bug, is there any alternative ways to check the actual status of each member as well as the Health check error status, thanks!

# neutron lbaas-loadbalancer-status test-lb
{
    "loadbalancer": {
        "name": "test-lb",
        "provisioning_status": "ACTIVE",
        "listeners": [
            {
                "name": "test-listener",
                "provisioning_status": "ACTIVE",
                "pools": [
                    {
                        "name": "test-pool",
                        "provisioning_status": "ACTIVE",
                        "healthmonitor": {
                            "provisioning_status": "ACTIVE",
                            "type": "HTTP",
                            "id": "69412b9d-b947-4199-8233-f138c4ad4526",
                            "name": "test-health-monitor"
                        },
                        "members": [
                            {
                                "name": "test-member-2",
                                "provisioning_status": "ACTIVE",
                                "address": "10.10.0.235",
                                "protocol_port": 80,
                                "id": "f54d0a52-c340-4d15-9e6a-8590caf16fac",
                                "operating_status": "ONLINE"
                            },
                            {
                                "name": "test-member-1",
                                "provisioning_status": "ACTIVE",
                                "address": "10.10.0.234",
                                "protocol_port": 80,
                                "id": "2539b7cc-f7d1-4e8b-be74-74fd252c9498",
                                "operating_status": "ONLINE"
                            }
                        ],
                        "id": "e0209289-c19d-4900-8251-4bea36881e05",
                        "operating_status": "ONLINE"
                    }
                ],
                "l7policies": [],
                "id": "1c058e3b-74b8-48c1-8e57-b49b83488c30",
                "operating_status": "ONLINE"
            }
        ],
        "pools": [
            {
                "name": "test-pool",
                "provisioning_status": "ACTIVE",
                "healthmonitor": {
                    "provisioning_status": "ACTIVE",
                    "type": "HTTP",
                    "id": "69412b9d-b947-4199-8233-f138c4ad4526",
                    "name": "test-health-monitor"
                },
                "members": [
            ...

[Ulysses (eperitus)]

Changing from incomplete back to new so this bug doesn't expire automatically, on behalf of bjzyang's comment #3.

sajuptpm: Thanks for the preliminary patch - did you see the reviewer's comments?

[Yang Zhang (bjzyang)]

Hello,

Is there any update on this bug? Or is there any alternative solution to get the actual status of members of load balancers via any "neutron lbaas" CLI command or API?

Thanks!

[Bernard Cafarelli (bcafarel)]

Closing this old launchpad, either it was fixed since last update, or if still valid please fill a story for neutron-lbaas at https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas