After neutron patch was merged I investigated again similar failure (https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_703/910366/1/check/cinder-plugin-ceph-tempest-mn-aa/703b88a/testr_results.html) and it seems that haproxy is spawned without any problems but the issue is somewhere else.
From what I found so far in this job is that there is no any OF rule in br-int (checked in journal log from compute1) but for other metadata ports I see rule like:
cookie=0x9e5e61a7, duration=19.734s, table=65, n_packets=0, n_bytes=0, idle_age=19, priority=100,reg15=0x1,metadata=0x9 actions=output:288
I proposed patch https://review.opendev.org/c/openstack/tempest/+/911673 to add ovs and ovn logs to the jobs' logs for all jobs based on devstack-tempest job. Lets see if that will help to understand that issue.
After neutron patch was merged I investigated again similar failure (https:/ /storage. bhs.cloud. ovh.net/ v1/AUTH_ dcaab5e32b234d5 6b626f72581e364 4c/zuul_ opendev_ logs_703/ 910366/ 1/check/ cinder- plugin- ceph-tempest- mn-aa/703b88a/ testr_results. html) and it seems that haproxy is spawned without any problems but the issue is somewhere else.
From what I found so far in this job is that there is no any OF rule in br-int (checked in journal log from compute1) but for other metadata ports I see rule like:
cookie=0x9e5e61a7, duration=19.734s, table=65, n_packets=0, n_bytes=0, idle_age=19, priority= 100,reg15= 0x1,metadata= 0x9 actions=output:288
I proposed patch https:/ /review. opendev. org/c/openstack /tempest/ +/911673 to add ovs and ovn logs to the jobs' logs for all jobs based on devstack-tempest job. Lets see if that will help to understand that issue.