Comment 3 for bug 2059716

Hi Fernando,

Mohammed has reported the bug on our behalf.

Our current environment is running the following versions of various networking components:
* octavia: 11.0.1
* ovn-octavia-provider: 4.0.1
* neutron-server: 21.2.1.dev48

on top of OVN 22.03.

There is a slight change in the setup you've done which makes one of the members to not be reachable in the above environment: the VM which becomes unreachable via the LB IP gets a floating IP attached before its IP is added as a member to the loadbalancer. Basically moving this part:

```
PORTVM3=$(openstack port list --fixed-ip ip-address=$IPVM03 -c ID -f value)
openstack floating ip create --port $PORTVM3 public

```
before the first `openstack loadbalancer member create...` command in your test.

Let us know if this changes anything on your side. We can consistently replicate it in our environment.

All the best,
Cristi