MAAS

~cgrabowski/maas:backport_fix_outside_of_zone_update_for_large_subnets_3.4

  1. Git
  2. lp:~cgrabowski/maas
  3. backport_fix_outside_of_zone_update_f...
Last commit made on 2023-11-02
Get this branch:
git clone -b backport_fix_outside_of_zone_update_for_large_subnets_3.4 https://git.launchpad.net/~cgrabowski/maas
Only Christian Grabowski can upload to this branch. If you are Christian Grabowski please log in for upload directions.

Branch merges

Branch information

Name:
backport_fix_outside_of_zone_update_for_large_subnets_3.4
Repository:
lp:~cgrabowski/maas

Recent commits

b1966d8... by Christian Grabowski

always use the DomainInfo network for reverse zones and check IP belongs to it

(cherry picked from commit b3dae13ec9a6b14f8c5cf23fb01de897c72256ca)

c955852... by Christian Grabowski

use network ip and prefixlen of subnet when reverse zone is not given
(cherry picked from commit 6febd214b36cd3db4ff70540f7a25e01705fa5b2)

05450ee... by Peter Makowski

Update maas-ui to 359edef50
fix: import images lp#2031614 (#5200) (#5201)

53d5ac1... by Alexsander de Souza

restore target used by maas-release-tools

cdc4d8e... by Alexsander de Souza

update PPA for building the snap

8054aed... by Alberto Donato

Prepare for 3.4.0 RC2 release

7f8d9e9... by Alberto Donato

LP:2037524 fix bigint migration for IDs, exclude Fabric since 0 value is used there too

backport of ba319aecf from master

dd2c36b... by Anton Troyanov

fix: change database owner

MAAS requires $dbc_dbuser to be an owner of $dbc_dbname.
One of the reasons is to be able to create new schemas (CREATE SCHEMA).

This is not new and documentation mentions the following configuration step:
```
sudo -u postgres \
  createdb -O \
  "$MAAS_DBUSER" \
  "$MAAS_DBNAME"
```

Unfortunately dbconfig-common used by MAAS configures `postgres` user as the
owner of `maasdb`.

Starting from dbconfig-common 2.0.22 the owner of the database
will be PostgreSQL user ($dbc_dbuser) [0]. For us this is the desired behavior.

Because dbconfig-common 2.0.22 is not available in 22.04, we have to fix
it ourselves for new installations and handle this case during upgrades
via deb packages.

In situations when MAAS cannot fix database ownership automatically we
want to inform MAAS user via deprecation notice [3].

[0]: https://salsa.debian.org/debian/dbconfig-common/-/blob/master/debian/changelog#L21
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010923
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021791
[3]: https://maas.io/deprecations/MD4

(cherry picked from commit ff9123154bd5041010f9032be7be8814d5e413cd)

0e3982d... by Jacopo Rota

add retry-after header in 409 responses - cherry pick e8aa5d01a5272c536a2aa3e23bd3fc11b580bd90

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