After discussing with my nova colleagues, this is not happening on wallaby/master because we started parsing firmware descriptor files as part of the secure boot work [1]
The proposed workaround of excluding edk2-ovmf-20200602gitca407c7246bf-5 seems to work and we recommend that we keep it until bz1961562 [2] mentioned above has a fix released.
There's another possible workaround if this is not possible anymore and that would involved creating files under /etc/qemu on the compute nodes as mentioned in comment #16 of that same bz
After discussing with my nova colleagues, this is not happening on wallaby/master because we started parsing firmware descriptor files as part of the secure boot work [1]
The proposed workaround of excluding edk2-ovmf- 20200602gitca40 7c7246bf- 5 seems to work and we recommend that we keep it until bz1961562 [2] mentioned above has a fix released.
There's another possible workaround if this is not possible anymore and that would involved creating files under /etc/qemu on the compute nodes as mentioned in comment #16 of that same bz
mkdir -p /etc/qemu/firmware firmware/ 50-edk2- ovmf-cc. json
touch /etc/qemu/
This will create an empty file which can disable the new firmware, more details here [2], look for firmware description.
[1] https:/ /github. com/openstack/ nova/blob/ b0cd985f0c09088 098f74cc0cb1df6 16cc0ef12b/ nova/virt/ libvirt/ host.py# L1601-L1664 /bugzilla. redhat. com/show_ bug.cgi? id=1961562 /libvirt. org/formatdomai n.html# operating- system- booting
[2] https:/
[3] https:/