Comment 2 for bug 1968732

Had a quick look and looks like issue is random as it has both pass and failure run across multiple runs[1][2]. Temporary it's ok to add test to skiplist until the issue is root caused.

Also didn't find any similar failure in master so looks wallaby specific.

The issue is happening as metadata request from vm are failing[3] as below, and as per metadata agent log[4], no request received for the server 2a0389f3-c36c-4ec1-ac80-81cfbb380d4f(ip 10.100.0.6).

checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 12.55. request failed
failed 2/20: up 61.73. request failed
failed 3/20: up 110.92. request failed
failed 4/20: up 160.16. request failed
failed 5/20: up 209.38. request failed
failed 6/20: up 258.58. request failed

[1] https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-9-containers-multinode-wallaby&skip=0
[2] https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-9-containers-multinode&branch=stable%2Fwallaby&skip=0
[3] https://88e7be3fd9763a3635e4-f525513b10cd88ade5723da63b385b8c.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/tripleo-ci/master/tripleo-ci-centos-9-containers-multinode-wallaby/a881ed1/logs/undercloud/var/log/tempest/stestr_results.html
[4] https://88e7be3fd9763a3635e4-f525513b10cd88ade5723da63b385b8c.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/tripleo-ci/master/tripleo-ci-centos-9-containers-multinode-wallaby/a881ed1/logs/subnode-1/var/log/containers/neutron/ovn-metadata-agent.log