[2.1] Node commissioning failure - 'cloudinit' running config-ntp when node does not have route to the archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned |
Bug Description
Commissioning fails with:
Node commissioning failure - 'cloudinit' running config-ntp with frequency once-per-instance
Node commissioning failure - 'cloudinit' running modules for config
It looks like APT HTTP proxy (maas-proxy) is not applied when running ntp module in cloud-init. The MAAS DHCP network does not have default gateway (isolated network), but MAAS itself has Internet access and offer an access to archive.ubuntu.com / security.ubuntu.com through maas-proxy.
See. attached rsyslog output.
[module ntp]
Oct 1 15:35:46 nearby-husky [CLOUDINIT] stages.py[DEBUG]: Running module ntp (<module 'cloudinit.
ncy once-per-instance
...
Oct 1 15:35:47 nearby-husky cloud-init[992]: Err:6 http://
Oct 1 15:35:47 nearby-husky cloud-init[992]: Cannot initiate the connection to security.
...
Oct 1 15:35:48 nearby-husky [CLOUDINIT] handlers.py[DEBUG]: finish: modules-
[module scripts-user]
Oct 1 15:35:52 nearby-husky [CLOUDINIT] stages.py[DEBUG]: Running module scripts-user (<module 'cloudinit.
ipts_user.py'>) with frequency once-per-instance
...
Oct 1 15:36:04 nearby-husky cloud-init[1195]: Get:21 http://