xena: wallaby merge #345
xena: wallaby merge #345
Conversation
(cherry picked from commit ee30588)
Update magnum_tag
The file 50-edk2-ovmf-cc.json is used by Nova in get_loader() when
lauching UEFI instances without Secure Boot.
It only supports machine type pc-q35-rhel8.5.0. However, with recent
nova-compute container images built on CentOS Stream 8, the machine type
is pc-q35-rhel8.6.0, which results in failures to launch instances with:
nova.exception.UEFINotSupported: UEFI is not supported
There is a fix for RHEL9/c9s [1], but not for RHEL8/c8s. Also see [2]
for more details.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2090752
[2] https://bugs.launchpad.net/nova/+bug/1955035
Patch edk2-ovmf file to fix UEFI support
See #339 for context.
Use Rocky Linux 8.7 repositories
While not pretty, this workaround avoids manual intervention after the runner is power cycled. Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
CI: Workaround container image builder power cycle issue
Deploy Nova images with edk2-ovmf UEFI fix
|
Is this the proper way of merging changes from one branch to another? I believe CI will automatically create a Git tag after the merge, and it will look like this tag has the UEFI fix (because there is the release note), while I still need to build Nova images for Xena and bump the container image tag. |
I usually just merge one branch into the next, then check the diff and make any changes necessary for the current branch. In this case that should probably include building a container and bumping the tag. |
|
I have triggered a nova container build using this branch: https://github.com/stackhpc/stackhpc-kayobe-config/actions/runs/3967356367 |
No description provided.