Run Temporal schema migration [0] as a part of `maas migrate`
- temporal is a general schema for Temporal data
- temporal_visibility is for Temporal Visibility service [1]
Dependency changes:
- 1.20.3-1-0ubuntu1 is the minimal supported, because it has SQL schema
- snap needs var/lib/maas/temporal since it contains migration schema
Update maas-ui to e2f9d3ed1
chore: upgrade react components (#5123)
- update tests to hover a tooltip trigger before running assertions
- add `expectTooltipOnHover` test util to reduce repetition
- fix react type resolution issues and type errors
MAAS GRUB chainloads the distro to save time that otherwise the system
would spend trying to netboot with all capable NICs.
Investigating LP:2022084, we discovered that with this chain, RHEL GRUB2
tries to validate the kernel using MAAS shim, causing the secure boot
process to fail. Given the nature of shim and secure boot process in
general, there's not much we can do on MAAS side to fix this behaviour.
As a hotfix, we temporarily drop the chainloading for other distros so
that they could boot securely (even though with some extra wait time).
Ubuntu will still be chainloaded because the MAAS shim trusts the certs
our kernels/bootloaders are signed with. I also don't think Windows
boot loader can be affected by any shims whatsoever, so MAAS will still
try to chainload it.