~alexsander-souza/maas:lp2028284_smart_sync_hints

Last commit made on 2023-08-25
Get this branch:
git clone -b lp2028284_smart_sync_hints https://git.launchpad.net/~alexsander-souza/maas
Only Alexsander de Souza can upload to this branch. If you are Alexsander de Souza please log in for upload directions.

Branch merges

Branch information

Name:
lp2028284_smart_sync_hints
Repository:
lp:~alexsander-souza/maas

Recent commits

3a354cf... by Alexsander de Souza

don't save hints if nothing changed

fixes LP#2028284

8371cf9... by Alexsander de Souza

fix DHCP notification handler

normalise MAC addresses before searching the database

fixes LP#2025468

f92038d... by Peter Makowski

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

454db5a... by Peter Makowski

Update maas-ui to 0ad385fd7
feat(machines) bulk failure reason MAASENG-1689 (#5124)

- add failureDetails to redux store machine slice
- create ErrorDetails component
- create MachineHostname component fetching machine details based on systemId

f3b643e... by Igor Brovtsin

Disable chainloading for third-party distros to fix secure boot

The usual MAAS local boot chain for well-known distros looks like this:

PXE -> MAAS shim -> MAAS GRUB2 -> Distro shim (if any) -> Distro loader

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.

e9d6c2e... by Anton Troyanov

refactor: opts pattern to override pool defaults

287a825... by Bill Wear

Update maas-offline-docs to 83baee6f
copy updated firewall link from discourse updates into master copy

d6217dd... by Bill Wear

Update maas-offline-docs to 2e86a299
commit discourse changes for topic 5196

95e809e... by Bill Wear

Update maas-offline-docs to 6bd60adc
fix output of spelling and diction runs

c3037f2... by Bill Wear

Update maas-offline-docs to d4946134
commit discourse changes for topic 6662