Hello,

we observe the following issue when running py39 job in Component CI for OSP 17 and 17.1

```
{10} nova.tests.unit.virt.disk.test_api.APITestCase.test_can_resize_need_fs_type_specified [175.554386s] ... FAILED

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/home/zuul/src/code.engineering.redhat.com/nova/nova/tests/unit/virt/disk/test_api.py", line 47, in test_can_resize_need_fs_type_specified
        self.assertFalse(api.is_image_extendable(image))
      File "/home/zuul/src/code.engineering.redhat.com/nova/nova/virt/disk/api.py", line 190, in is_image_extendable
        fs.setup(mount=False)
      File "/home/zuul/src/code.engineering.redhat.com/nova/nova/virt/disk/vfs/guestfs.py", line 235, in setup
        self.handle.launch()
      File "/usr/lib/python3.9/site-packages/eventlet/tpool.py", line 190, in doit
        result = proxy_call(self._autowrap, f, *args, **kwargs)
      File "/usr/lib/python3.9/site-packages/eventlet/tpool.py", line 148, in proxy_call
        rv = execute(f, *args, **kwargs)
      File "/usr/lib/python3.9/site-packages/eventlet/tpool.py", line 121, in execute
        rv = e.wait()
      File "/usr/lib/python3.9/site-packages/eventlet/event.py", line 125, in wait
        result = hub.switch()
      File "/usr/lib/python3.9/site-packages/eventlet/hubs/hub.py", line 313, in switch
        return self.greenlet.switch()
      File "/usr/lib/python3.9/site-packages/eventlet/hubs/hub.py", line 365, in run
        self.wait(sleep_time)
      File "/usr/lib/python3.9/site-packages/eventlet/hubs/poll.py", line 80, in wait
        presult = self.do_poll(seconds)
      File "/usr/lib/python3.9/site-packages/eventlet/hubs/epolls.py", line 31, in do_poll
        return self.poll.poll(seconds)
      File "/usr/lib/python3.9/site-packages/fixtures/_fixtures/timeout.py", line 52, in signal_handler
        raise TimeoutException()
    fixtures._fixtures.timeout.TimeoutException
    

Captured pythonlogging:
~~~~~~~~~~~~~~~~~~~~~~~
    2022-10-18 14:46:01,756 WARNING [oslo_policy.policy] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
    2022-10-18 14:46:01,756 WARNING [oslo_policy.policy] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html.
    2022-10-18 14:46:01,758 WARNING [oslo_policy.policy] Policy Rules ['os_compute_api:extensions', 'os_compute_api:os-floating-ip-pools', 'os_compute_api:os-quota-sets:defaults', 'os_compute_api:os-availability-zone:list', 'os_compute_api:limits', 'system_admin_api', 'system_reader_api', 'project_admin_api', 'project_member_api', 'project_reader_api', 'system_admin_or_owner', 'system_or_project_reader', 'os_compute_api:limits:other_project', 'os_compute_api:os-lock-server:unlock:unlock_override', 'os_compute_api:servers:create:zero_disk_flavor', 'compute:servers:resize:cross_cell'] specified in policy files are the same as the defaults provided by the service. You can remove these rules from policy files which will make maintenance easier. You can detect these redundant rules by ``oslopolicy-list-redundant`` tool also.
```

May this issue be related to the listed warnings from oslo_policy?

You may use this change to trigger the build by commenting "recheck": https://code.engineering.redhat.com/gerrit/c/nova/+/430672

Yours, Szymon