Failed to synchronise boot resources: Child Workflow execution failed

Users
1

Hi,
I’m using MAAS 3.6.2 since almost 2 mounths and all was working. However, today I logged on the API and I have the following error : “Failed to synchronise boot resources: Child Workflow execution failed”. On images window, I have the message “Step 1/2: Region controller importing” and one of my image (the 24.04 LTS) is “Queued for download”.
How can I fix this problem?

2

Hi @hugobert1

Oh, thats unfortunate. Anything interesting in the logs?
I am wondering if that could be a similar issue?

3

It seems to be something similar to these issue. I have almost the same logs. However, one of my images is synced : the 22.04 image is synced wheras the 24.04 image is queued for downlaod

4

Anything interesting in the logs?

5

I have these :
Jan 06 14:21:02 rancher maas-regiond[1626]: Traceback (most recent call last):
Jan 06 14:21:02 rancher maas-regiond[1626]: File “/snap/maas/40614/usr/lib/python3/dist-packages/temporalio/worker/_activity.py”, line 453, in _run_activity
Jan 06 14:21:02 rancher maas-regiond[1626]: result = await impl.execute_activity(input)
Jan 06 14:21:02 rancher maas-regiond[1626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jan 06 14:21:02 rancher maas-regiond[1626]: File “/snap/maas/40614/usr/lib/python3/dist-packages/temporalio/worker/_activity.py”, line 711, in execute_activity
Jan 06 14:21:02 rancher maas-regiond[1626]: return await input.fn(*input.args)
Jan 06 14:21:02 rancher maas-regiond[1626]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jan 06 14:21:02 rancher maas-regiond[1626]: File “/snap/maas/40614/lib/python3.12/site-packages/maasserver/workflow/bootresource.py”, line 253, in download_bootresourcefile
Jan 06 14:21:02 rancher maas-regiond[1626]: raise ApplicationError(
Jan 06 14:21:02 rancher maas-regiond[1626]: temporalio.exceptions.ApplicationError: ClientOSError: Connection reset by peer
Jan 06 14:21:11 rancher maas-regiond[2462]: regiond: [info] GET /MAAS/rpc/ HTTP/1.1 → 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
Jan 06 14:21:41 rancher maas-regiond[2457]: regiond: [info] GET /MAAS/rpc/ HTTP/1.1 → 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
Jan 06 14:21:51 rancher maas-regiond[1626]: maasserver.region_controller: [warn] The dynamic dns update notification ‘’ is not valid. It will be dropped.
Jan 06 14:21:54 rancher maas-regiond[1626]: maasserver.region_controller: [info] Reloaded DNS configuration:
Jan 06 14:21:54 rancher maas-regiond[1626]: * ip …
Jan 06 14:22:02 rancher maas-regiond[1626]: temporalio.activity: [warn] Completing activity as failed ({‘activity_id’: ‘1’, ‘activity_type’: ‘download-bootresourcefile’, ‘attempt’: 11, ‘namespace’: ‘default’, ‘task_queue’: ‘region-internal’, ‘workflow_id’: ‘download-bootresource:upstream:3d79e2c64519’, ‘workflow_run_id’: ‘fc04c5be-686d-4962-b2fc-1b8e9c64cc0d’, ‘workflow_type’: ‘download-bootresource’})

So I see that there are errors with _activity.py and bootresource.py such as the issue that you send, but there are also some other problems and I don’t understand why

6

Hi @hugobert1

The error relative to the image downloads is ClientOSError: Connection reset by peer, which doesn’t tell us much unfortunately.

Couple of questions for you:

  • where do you pull images from? images.maas.io, local mirror, other option?
  • do you have enough space on disk for all the images?
7

I upgrade maas in 3.7/stable version and it’s now working

8

Hey, I am having the same issue, with Ubuntu24.04 LTS amd64 image.
stuck in downloading though forever.
I upgraded to MAAS 3.7/stable and still have the same issue.

9

Hi, you might want to inspect the maas-temporal-worker or maas-region logs

journalctl -t maas-regiond
journalctl -t maas-temporal-worker