unable to deploy VM from vmdk

Issue

• Deploying a VM on ephemeral disk with a vmdk worked in rhosp 13 but in 16.2 it fails with the following:

error message:
test-eph
Overview
Interfaces
Log
Console
Action Log
Name
test-eph
ID
224f2fc7-ca8e-47fa-afa7-d89b752e6bcf
Description
-
Project ID
abc507b981ae4c65a9b22407af7f4fa4
Status
Error
Locked
False
Availability Zone
nova
Created
May 5, 2022, 1:12 p.m.
Age
9 minutes
Fault
Message
No valid host was found.
Code
500
Details
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 1379, in schedule_and_build_instances instance_uuids, return_alternates=True) File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 839, in _schedule_instances return_alternates=return_alternates) File "/usr/lib/python3.6/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations instance_uuids, return_objects, return_alternates) File "/usr/lib/python3.6/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/client.py", line 181, in call transport_options=self.transport_options) File "/usr/lib/python3.6/site-packages/oslo_messaging/transport.py", line 129, in _send transport_options=transport_options) File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 674, in send transport_options=transport_options) File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 664, in _send raise result nova.exception_Remote.NoValidHost_Remote: No valid host was found. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 235, in inner return func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/nova/scheduler/manager.py", line 199, in select_destinations raise exception.NoValidHost(reason="") nova.exception.NoValidHost: No valid host was found.
Created
May 5, 2022, 1:12 p.m.

• We see the following in /var/log/containers/nova/nova-scheduler.log:

2022-05-05 13:12:57.295 24 DEBUG nova.scheduler.manager [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] Starting to schedule for instances: ['224f2fc7-ca8e-47fa-afa7-d89b752e6bcf'] select_destinations /usr/lib/python3.6/site-packages/nova/scheduler/manager.py:133
2022-05-05 13:12:57.297 24 DEBUG nova.scheduler.request_filter [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] require_image_type_support request filter added required trait COMPUTE_IMAGE_TYPE_VMDK require_image_type_support /usr/lib/python3.6/site-packages/nova/scheduler/request_filter.py:195
2022-05-05 13:12:57.297 24 DEBUG nova.scheduler.request_filter [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] Request filter 'require_image_type_support' took 0.0 seconds wrapper /usr/lib/python3.6/site-packages/nova/scheduler/request_filter.py:44
2022-05-05 13:12:57.298 24 DEBUG nova.scheduler.request_filter [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] compute_status_filter request filter added forbidden trait COMPUTE_STATUS_DISABLED compute_status_filter /usr/lib/python3.6/site-packages/nova/scheduler/request_filter.py:217
2022-05-05 13:12:57.299 24 DEBUG nova.scheduler.request_filter [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] Request filter 'compute_status_filter' took 0.0 seconds wrapper /usr/lib/python3.6/site-packages/nova/scheduler/request_filter.py:44
2022-05-05 13:12:57.573 24 INFO nova.scheduler.manager [req-87868e1b-e7fb-4c54-a7fb-993003816465 45c484ea1e824635aa48fc8c6b43ea2c abc507b981ae4c65a9b22407af7f4fa4 - default default] Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up.