~alexsander-souza/maas:lp2063835_to_3_5

Last commit made on 2024-04-26
Get this branch:
git clone -b lp2063835_to_3_5 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:
lp2063835_to_3_5
Repository:
lp:~alexsander-souza/maas

Recent commits

f404a65... by Alexsander de Souza

fix(bootresources): handle incomplete files

if a resource was partially downloaded at the time of the migration,
discard the large object and schedule it for downloading again.

(cherry picked from commit 811612c009dc8c095c3b99062563801e3a991967)

21bc85f... by Christian Grabowski

fix: handle BIND failures when notifies are delayed
(cherry picked from commit 19ac75f3d5e2bcb7d4934579aa94717dc1823104)

dc50b53... by Anton Troyanov

fix(agent): check if region endpoints are reachable

Region Controller might return IP:PORT that is not reachable by the
Agent (due to firewall configuration or network setup). Hence we should
add check if endpoints are reachable before applying them as targets
when configuring Agent HTTP reverse proxy service.

Resolves LP:2063220

Workflow logic is constrained by deterministic execution requirements.
In Go, Workflow Definition code cannot directly do the following:
- Call an external API, conduct a file I/O operation, talk to another service, etc

Normally we should use Activity for this scenario, however we are
confident and consider that we want to do this I/O inside the workflow.

But by having a blocking I/O you might get the following panic:
```
panic: Potential deadlock detected: workflow goroutine "root" didn't yield for over a second
```

It happens simply because the "root" goroutine was not scheduled for
execution. By using `workflow.Go` we don't mess with the scheduler and
we should worry about logic inside `workflow.Go` not take more than 1
second.

(cherry picked from commit 17596243156a800d060b8c5138798da8eae0950b)

0554882... by Nick De Villiers

Update maas-ui to 614cefd65
chore: cut v3.5.0 (#5400)

f87db74... by Jacopo Rota

Prepare for 3.5.0 RC2 release

6c740e5... by Alexsander de Souza

feat(bootresources): check if the controller has enough space

- don't export images from DB if they don't fit in the disk
- don't retry downloads on out-of-disk errors, let the user fix this first
- notify the user about out-of-disk errors

(cherry picked from commit 194a121188e58116833c782dd71b1b7fafd7ce50)

6772474... by Jacopo Rota

fix: lp-2060687. Ensure release scripts are Included for machines in DISK_ERASING status.

(cherry-picked from 2557926e567cba41a859aa5f5682978153a6efa8)

66b8e14... by Peter Makowski

Update maas-ui to 5360f7f14
fix: device details subnet on load MAASENG-3036 (#5394)

5f658fb... by Alessandro Marcolini

 fix: bug lp#2060277
https://bugs.launchpad.net/maas/+bug/2060277

(cherry-picked from e7cbf290608a8c7b25268424f43b706bd8de4ae8)

4ccc372... by "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>

Update maas-ui to 9218dee4f
chore(deps): bump vite from 5.1.4 to 5.2.6 (#5390)

Signed-off-by: dependabot[bot] <email address hidden>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>