Further testing on our has shown that the issue seems to be manifesting only if the loadbalancer VIP is directly created on the provider network, but not when the VIP is created on the tenant network and then gets a floating IP assigned to it.
So, in this scenario, we can probably advise users to create the VIP on the tenant network and add a floating IP to it, however, would there be a way to enforce this policy (prevent the user from creating the LB VIP directly on the provider network)?
Hi Fernando,
Further testing on our has shown that the issue seems to be manifesting only if the loadbalancer VIP is directly created on the provider network, but not when the VIP is created on the tenant network and then gets a floating IP assigned to it.
So, in this scenario, we can probably advise users to create the VIP on the tenant network and add a floating IP to it, however, would there be a way to enforce this policy (prevent the user from creating the LB VIP directly on the provider network)?
Thank you,
Cristi