Same scenario described on the bug works out of the box on an OpenStack environment using ML2/OVS instead of OVN
Same scenario described on the bug works out of the box on an OpenStack environment using ML2/OVS instead of OVN