Public bug reported:
I'm trying to deploy machines from MAAS that are configured with 2 LACP bonds.
However, it always fails during the cloud-init phase where it tries to fetch
metadata from MAAS.
The following is the excerpt where the error is shown.
[ 20.932832] cloud-init[2315]: 2025-04-09 08:43:06,461 -
handlers.py[WARNING]: Failed posting event: {"name":
"init-network/check-cache", "description": "attempting to read from cache
[trust]", "event_type": "start", "origin": "cloudinit", "timestamp":
1744188183.3420255}. This was caused by: HTTPConnectionPool(host='172.16.46.1',
port=5248): Max retries exceeded with url: /MAAS/metadata/status/xx6pyb (Caused
by NewConnectionError('<urllib3.connection.HTTPConnection object at
0x74262cad9fc0>: Failed to establish a new connection: [Errno 113] No route to
host'))
[ 20.992495] cloud-init[2315]: 2025-04-09 08:43:06,463 -
log_util.py[WARNING]: Failed fetching metadata from url
http://172.16.46.1:5248/MAAS/metadata/
[ 21.010338] cloud-init[2315]: 2025-04-09 08:43:06,469 -
log_util.py[WARNING]: No instance datasource found! Likely bad things to come!
[ OK ] Stopped Wait for Network to be Configured.
Stopping Wait for Network to be Configured...
Stopping Network Configuration...
[ OK ] Stopped Network Configuration.
Starting Network Configuration...
[ OK ] Started Network Configuration.
Starting Wait for Network to be Configured...
[ OK ] Finished Wait for Network to be Configured.
[ 24.004804] cloud-init[2315]: 2025-04-09 08:43:09,533 -
handlers.py[WARNING]: Failed posting event: {"name":
"init-network/check-cache", "description": "no cache found", "event_type":
"finish", "origin": "cloudinit", "timestamp": 1744188183.3423693, "result":
"SUCCESS"}. This was caused by: HTTPConnectionPool(host='172.16.46.1',
port=5248): Max retries exceeded with url: /MAAS/metadata/status/xx6pyb (Caused
by NewConnectionError('<urllib3.connection.HTTPConnection object at
0x74262cada5c0>: Failed to establish a new connection: [Errno 113] No route to
host')) [ 27.076636]
cloud-init[2315]: 2025-04-09 08:43:12,605 - handlers.py[WARNING]: Failed
posting event: {"name": "init-network/search-MAAS", "description":
"searching for network data from DataSourceMAAS", "event_type": "start",
"origin": "cloudinit", "timestamp": 1744188183.3493934}. This was caused by:
HTTPConnectionPool(host='172.16.46.1', port=5248): Max retries exceeded with
url: /MAAS/metadata/status/xx6pyb (Caused by
NewConnectionError('<urllib3.connection.HTTPConnection object at
0x74262c754eb0>: Failed to establish a new connection: [Errno 113] No route to
host'))
[ 27.137462] cloud-init[2315]: 2025-04-09 08:43:12,605 -
handlers.py[WARNING]: Multiple consecutive failures in WebHookHandler.
Cancelling all queued events.
[FAILED] Failed to start Cloud-init: Network Stage.
This used to work before, and the server spec and the network configuration are
identical.
What I found is that if I configure only one LACP bond, then the deployment
completes successfully.
I believe this is also related/similar to this bug[0].
I was able to workaround this when using the following curtin script.
However, since the older version is only available in Jammy, this will not work
with Noble.
#cloud-config
debconf_selections:
maas: |
{{for line in str(curtin_preseed).splitlines()}}
{{line}}
{{endfor}}
late_commands:
maas: [wget, '--no-proxy', {{node_disable_pxe_url|escape.json}},
'--post-data', {{node_disable_pxe_data|escape.json}}, '-O', '/dev/null']
cloud_init_downgrade: ["curtin", "in-target", "--", "apt-get", "install",
"-y", "--allow-downgrades", "cloud-init=23.1.2-0ubuntu0~22.04.1"]
[0] https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2100963
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106683
Title:
cloud-init fails with MAAS when having more than 2 bonds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2106683/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
