Public bug reported: I can deploy members with an invalid / invented ip address (no real servers with that address) and the LB shows that everything is ok with them (running `openstack loadbalancer status show <lb>` will show that the members have "operating_status": "ONLINE".
An example: I deployed the following: { "loadbalancer": { "id": "c50b7cb3-6b8f-434b-9a47-a10a27d0a9b5", "name": "ovn_lb", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "listeners": [ { "id": "87bafdda-0ac6-438f-8824-cb75f9e014df", "name": "tcp_listener", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "pools": [ { "id": "aa6ed64c-4d19-448b-969d-6cc686385162", "name": "tcp_pool", "provisioning_status": "ACTIVE", "operating_status": "ONLINE", "health_monitor": { "id": "cc72e7eb-722b-49be-b3d2-3857f880346d", "name": "hm_ovn_provider", "type": "TCP", "provisioning_status": "ACTIVE", "operating_status": "ONLINE" }, "members": [ { "id": "648b9d51-115a-4312-b92e-cc59af0d0401", "name": "fake_member", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.100.0.204", "protocol_port": 80 }, { "id": "8dae11a2-e2d5-45f9-9e85-50f61fa07753", "name": "de3f2a06", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.0.64.34", "protocol_port": 80 }, { "id": "9b044180-71b4-4fa6-83df-4d0f99b4a3f7", "name": "fake_member2", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.100.0.205", "protocol_port": 80 }, { "id": "fe9ce8ca-e6b7-4c5b-807c-8e295156df85", "name": "6c186a80", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.0.64.39", "protocol_port": 80 } ] } ] } ] } } when the existing servers are the following: +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ | ID | Name | Status | Networks | | | +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ | 1e4a4464-4bbf-4107-94e4-974e87c31074 | 8941a208 | ACTIVE | private=10.0.64.34, fd47:e41c:f56e:0:f816:3eff:fe9f:67f4 | | | | 1a0de4d2-d9ea-4d60-85ff-018bcc00d285 | tobiko_44801dfe | ACTIVE | private=10.0.64.39, fd47:e41c:f56e:0:f816:3eff:fea2:7af9 | | | +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ it happened to me a few times that I had typos when I created the member (I wrote the ip address wrong), seeing those members as ONLINE, it would have been much more difficult to me to understand what happened. ** Affects: neutron Importance: Undecided Assignee: Fernando Royo (froyoredhat) Status: In Progress ** Tags: ovn-octavia-provider ** Changed in: neutron Assignee: (unassigned) => Fernando Royo (froyoredhat) ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2034522 Title: Fake members operating_status ONLINE Status in neutron: In Progress Bug description: I can deploy members with an invalid / invented ip address (no real servers with that address) and the LB shows that everything is ok with them (running `openstack loadbalancer status show <lb>` will show that the members have "operating_status": "ONLINE". An example: I deployed the following: { "loadbalancer": { "id": "c50b7cb3-6b8f-434b-9a47-a10a27d0a9b5", "name": "ovn_lb", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "listeners": [ { "id": "87bafdda-0ac6-438f-8824-cb75f9e014df", "name": "tcp_listener", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "pools": [ { "id": "aa6ed64c-4d19-448b-969d-6cc686385162", "name": "tcp_pool", "provisioning_status": "ACTIVE", "operating_status": "ONLINE", "health_monitor": { "id": "cc72e7eb-722b-49be-b3d2-3857f880346d", "name": "hm_ovn_provider", "type": "TCP", "provisioning_status": "ACTIVE", "operating_status": "ONLINE" }, "members": [ { "id": "648b9d51-115a-4312-b92e-cc59af0d0401", "name": "fake_member", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.100.0.204", "protocol_port": 80 }, { "id": "8dae11a2-e2d5-45f9-9e85-50f61fa07753", "name": "de3f2a06", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.0.64.34", "protocol_port": 80 }, { "id": "9b044180-71b4-4fa6-83df-4d0f99b4a3f7", "name": "fake_member2", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.100.0.205", "protocol_port": 80 }, { "id": "fe9ce8ca-e6b7-4c5b-807c-8e295156df85", "name": "6c186a80", "operating_status": "ONLINE", "provisioning_status": "ACTIVE", "address": "10.0.64.39", "protocol_port": 80 } ] } ] } ] } } when the existing servers are the following: +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ | ID | Name | Status | Networks | | | +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ | 1e4a4464-4bbf-4107-94e4-974e87c31074 | 8941a208 | ACTIVE | private=10.0.64.34, fd47:e41c:f56e:0:f816:3eff:fe9f:67f4 | | | | 1a0de4d2-d9ea-4d60-85ff-018bcc00d285 | tobiko_44801dfe | ACTIVE | private=10.0.64.39, fd47:e41c:f56e:0:f816:3eff:fea2:7af9 | | | +--------------------------------------+-----------------+--------+----------------------------------------------------------+----------------------------------------------------+------------+ it happened to me a few times that I had typos when I created the member (I wrote the ip address wrong), seeing those members as ONLINE, it would have been much more difficult to me to understand what happened. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2034522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp