I've performed another test on this...

Creating the scenario resembling the magnum setup with simple vm's.

- create 6 vm's, install apache2
- edit /etc/apache2/ports.conf to Listen 80 Listen 8080 Listen 9090 and 
restart. curl locally to check its working.
- create security group to allow 80,8080,9090
- create a load balancer with three listeners, on 80, 8080, and 9090.
- create three pools using SOURCE_IP_PORT, one for 80 on vm1 and vm2, another 
for 8080 on vm3 and vm4, and finally for 9090 on vm5 and vm6.
- create health monitors for TCP.
- assign a floating ip to the load balancer.

Results at this point:-

- port 80 will work, 8080 and 9090 will timeout.


Further testing

- transfer the pool for the port 80 listener to use members vm5 and vm6.Port 80 
will still work. 8080 and 9090 still timeout.
- delete the listener and pool for 80, it will still work. 8080 and 9090 still 
timeout.
- delete the listener and pool for 8080, port 80 will still work. 8080 and 9090 
still timeout.
- delete vm5 and vm6 - port 80 STILL WORKS!!! 8080 and 9090 still timeout.
- delete vm1 and vm2 (where port 80 was originally) and port 80 stops 
responding. 8080 and 9090 still timeout.
- repoint the listener for 9090 to vm3 and vm4. Nothing responds.


Summary

It appears the LB is setup with the first listener and pool/members
regardless, and no other traffic can work even if the healthcheck
scenario seen on magnum was to be resolved. For the use of Sunbeam and
Magnum, ovn doesn't appear to function as needed and contains
showstopping issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091931

Title:
  Issues with OVN-based Octavia

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-openstack/+bug/2091931/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to