MAAS

maas:3.4

  1. Git
  2. lp:maas
  3. 3.4
Last commit made on 2024-12-03
Get this branch:
git clone -b 3.4 https://git.launchpad.net/maas
Members of MAAS Committers can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
3.4
Repository:
lp:maas

Recent commits

9aaecd5... by Christian Grabowski

fix: Ensure hostname complies with RFC
FQDN have to be formatted according to RFC 952. This change ensures that
interface name derived hostnames comply with this format.
Resolves LP:2072155
Signed-off-by: Nicolas Bock <email address hidden>

(cherry picked from commit ee8810ea4a6dcf277248cb640dbdd3fa97cea21c)

a844813... by Jacopo Rota

fix: allow commissioning with bionic.

Resolves: LP:2073501
(cherry picked from commit 4cd1828f4e35703012844c84f5b0a509fd7e3b5a)

37cef29... by Ghadi Rahme

fix: Fix controller and rack version discrepancy. Currently rackd and regiond use two different ways to update the version number.
While rackd uses `get_running_version()` inside registerRackWithRegion(), regiond makes use of `get_versions_info()` during startup as well as periodically.

The problem is that `get_running_version()` returns a MAASVersion object which contains a simplified version string (no epoch for example), `get_versions_info()` return a DebVersionsInfo or a SnapVersionsInfo depending on the installation type, and the deb version of the installation will contain a full version string.

While rackd through registerRackWithRegion() will end up calling `set_version()` inside the `ControllerInfoManager` class. Other calls to update the version from regiond will end up in `set_version_info()` of the same class.
This patch fixes the issue by converting the version string inside the `set_version_info()` class to a MAASVersion object before returning the simplifies string value.
The same has been done for `update_version`.

Resolves: #LP2058063.
(cherry picked from commit 9f9013852b65c608b2e7ccfd8569eb17ef63ef41)

a41f860... by Andrew Lamzed-Short

feat(settings): Extended validation for IPMI k_g field in settings

Max tested length changed to 40 characters to accommodate hex-encoded k_g values. The value is passed to `ipmitool`, validated, with any errors caught and reported back through a new Django field validator.

Resolves LP:2055347

(cherry picked from commit fbc8681a271d90f37d95581dcd732c5116aa28ce)

a6896a6... by Seyeong Kim

fix(maasserver): Adding system_id for filtering in UI

Adding system_id for filtering

Resolves LP:2078810

(cherry picked from commit 1513d28998088bfca309e2f6e5ed8c5d1517e04f)

ae5e072... by Jacopo Rota

fix(maasserver): the StatusMonitorService should not be stopped if one recurrent job fails

fixes LP#2084788

(cherry picked from commit 31d5ef95479b49ab602b294a4a4d2437329ecde4)

2137323... by Dariusz Gadomski

fix: distro_series and osystem check based on node status

Resolves LP:2040324

(cherry picked from commit 1fadea85660b4c53f255f38fa22475a5a42db0c0)

ab434d5... by Jacopo Rota

Prepare for 3.4.5 release

c4e151c... by Jacopo Rota

fix: do not add neighbour during deployment if an ip address is in use

Resolves LP:2024242

(cherry picked from commit 0144c504d72cff6e4a02fc89ba26e0774fe0b31c)

340b02c... by Jacopo Rota

fix(redfish): handle Reset status in Redfish power driver.

HPE Gen11 (and above) BMC might return a "Reset" or an "Unknown" status. Such statuses are transitional, so the BMC will eventually return another "known" status.
For such reason, with this change the MAAS Redfish power driver is going to retry up to 7 times to get a "known" status. If the maximum number of retries is reached, an error is returned.

Resolves: #LP2079797

(Cherry-picked from e9830dcbf6a38409c890310d972b589521fa3d3d)