We're running into the same issue. I've used the same workaround using traits as Dylan mentioned in #3.
For future travellers, these were my steps:
openstack trait create CUSTOM_VGPU_PLACEMENT
# the VFs/BDFs I'm grepping for are the ones already allocated to a mdev on the machine
for uuid in $(openstack resource provider list | grep -e 0000_25_00_6 -e 0000_25_01_3 -e 0000_25_03_0 -e 0000_25_03_3 -e 0000_25_03_6 -e 0000_25_04_1 | awk '{print $2}'); do openstack resource provider trait set --trait CUSTOM_VGPU_PLACEMENT $uuid;done
openstack flavor set <my_flavor> --property trait:CUSTOM_VGPU_PLACEMENT=required
We're running into the same issue. I've used the same workaround using traits as Dylan mentioned in #3. VGPU_PLACEMENT
For future travellers, these were my steps:
openstack trait create CUSTOM_
# the VFs/BDFs I'm grepping for are the ones already allocated to a mdev on the machine VGPU_PLACEMENT $uuid;done
for uuid in $(openstack resource provider list | grep -e 0000_25_00_6 -e 0000_25_01_3 -e 0000_25_03_0 -e 0000_25_03_3 -e 0000_25_03_6 -e 0000_25_04_1 | awk '{print $2}'); do openstack resource provider trait set --trait CUSTOM_
openstack flavor set <my_flavor> --property trait:CUSTOM_ VGPU_PLACEMENT= required