~r00ta/maas:lp-2034014-add-retry-header-for-409-responses-3.4

Last commit made on 2023-09-12
Get this branch:
git clone -b lp-2034014-add-retry-header-for-409-responses-3.4 https://git.launchpad.net/~r00ta/maas
Only Jacopo Rota can upload to this branch. If you are Jacopo Rota please log in for upload directions.

Branch merges

Branch information

Name:
lp-2034014-add-retry-header-for-409-responses-3.4
Repository:
lp:~r00ta/maas

Recent commits

1a48d9b... by Jacopo Rota

add retry-after header in 409 responses

d15060d... by Peter Makowski

Update maas-ui to 5565f5f0f
fix(websocket): refetch on reconnect MAASENG-2142 (#5146) 3.4 backport (#5152)

- add `connectedCount` to redux store
- stop WebSocket ping on disconnect
- run invalidateQueries on disconnect
- run `useFetchActions` hook on reconnect
- test: update Preferences.test.tsx

8a3f6c8... by Ubuntu <email address hidden>

Fix reverse order ip address

When controller's nic has several ip and virtual ip,
SQL collect them reverse order. this fixes it.

backport of cfe8cf628 from master

0ff66ff... by Peter Makowski

Update maas-ui to 4f99547eb
fix: storage layout allocated machines lp#1928623 (#5136) (#5143)

d82e20c... by Alexsander de Souza

don't save hints if nothing changed

fixes LP#2028284

(cherry picked from commit 47c507d3867ba3621c7669cfacefd910757a81ae)

8657404... 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.

(cherry picked from commit f3b643e5f40f171326df134a0827a93fdc0137e4)

0737b67... by Jacopo Rota

Backport 7cd2755de2551b827f0fe86828e7c1b7273f8701 - Fix "The handler is closed" exception in the AMP unhandledError

bb0dc28... by Alexsander de Souza

fix DHCP notification handler

normalise MAC addresses before searching the database

fixes LP#2025468

(cherry picked from commit 8371cf9e2d46dd3c4103c6af08776ce1bb1cc5dc)

5d19113... by Alexsander de Souza

add support to quirks in the ephemeral kernel during xinstall

Some older OSes (like Centos/7) require that we tune the ephemeral OS kernel to match the capabilities of the one being deployed.

(cherry picked from commit 52f344ab28c0e615dcefc134922191fb6b944a9c)

431faeb... by Alberto Donato

set build PPA to ppa:maas/3.4-next