Wily daily MAAS cloud image fails to fully install.

Bug #1488507 reported by Brad Figg
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Undecided
Unassigned

Bug Description

Aug 24 20:47:32 ubuntu cloud-init[804]: 2015-08-24 20:47:32,158 - util.py[WARNING]: Getting data from <class cloudinit.sources.DataSourceMAAS.DataSourceMAAS'> failed
Aug 24 20:47:32 ubuntu pollinate[850]: ERROR: Network communication failed [6]\n % Total % Received % Xferd Average Speed Time Time Time Current#012 Dload Upload Total Spent Left Speed#012#015 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 020:47:32.316865 * Could not resolve host: entropy.ubuntu.com#01220:47:32.316975 * Closing connection 0#012curl: (6) Could not resolve host: entropy.ubuntu.com
Aug 24 20:47:32 ubuntu pollinate[706]: Aug 24 20:47:32 ubuntu <13>Aug 24 20:47:32 pollinate[850]: ERROR: Network communication failed [6]\n % Total % Received % Xferd Average Speed Time Time Time Current
Aug 24 20:47:32 ubuntu pollinate[706]: Dload Upload Total Spent Left Speed
Aug 24 20:47:32 ubuntu pollinate[706]: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 020:47:32.316865 * Could not resolve host: entropy.ubuntu.com
Aug 24 20:47:32 ubuntu pollinate[706]: 20:47:32.316975 * Closing connection 0
Aug 24 20:47:32 ubuntu pollinate[706]: curl: (6) Could not resolve host: entropy.ubuntu.com
Aug 24 20:47:32 ubuntu systemd[1]: pollinate.service: Main process exited, code=exited, status=1/FAILURE
Aug 24 20:47:32 ubuntu systemd[1]: Failed to start Seed the pseudo random number generator on first boot.
Aug 24 20:47:32 ubuntu systemd[1]: pollinate.service: Unit entered failed state.
Aug 24 20:47:32 ubuntu systemd[1]: pollinate.service: Failed with result 'exit-code'.
Aug 24 20:47:42 ubuntu cloud-init[804]: 2015-08-24 20:47:42,170 - DataSourceCloudSigma.py[WARNING]: failed to get hypervisor product name via dmi data
Aug 24 20:47:42 ubuntu cloud-init[804]: 2015-08-24 20:47:42,171 - util.py[WARNING]: Getting data from <class 'cloudinit.sources.DataSourceSmartOS.DataSourceSmartOS'> failed
Aug 24 20:48:32 ubuntu cloud-init[804]: 2015-08-24 20:48:32,226 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd6503fe048>, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))]
Aug 24 20:49:23 ubuntu cloud-init[804]: 2015-08-24 20:49:23,285 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd6503f11d0>, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))]

See the attached syslog.

Related branches

Revision history for this message
Brad Figg (brad-figg) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Ryan Harper (raharper) wrote :

Brad, do you have any maas logs for the time when the failure occurred?

It appears that MAAS was rejecting the request for metadata:

Aug 24 20:49:42 ubuntu cloud-init[804]: 2015-08-24 20:49:42,331 - url_helper.py[WARNING]: Calling 'http://10.10.10.1/latest/meta-data/instance-id' failed [0/120s]: request error [('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))]

10.10.10.1 is the router, but that looks like an odd URL for MAAS, please confirm that's correct.

Revision history for this message
Ryan Harper (raharper) wrote :

Ryan,

juju attempted to install a systemd service and systemd doesn't like the format (or maybe location):

I can reproduce this in any current wily instance by repeating the steps from the script (as seen in cloud-init-output.log):

+ install -D -m 644 /dev/null /etc/systemd/system/juju-clean-shutdown.service
+ printf %s\n
[Unit]
Description=Stop all network interfaces on shutdown
DefaultDependencies=false
After=final.target

[Service]
Type=oneshot
ExecStart=/sbin/ifdown -a -v --force
StandardOutput=tty
StandardError=tty

[Install]
WantedBy=final.target

+ /bin/systemctl enable /etc/systemd/system/juju-clean-shutdown.service
Failed to execute operation: Unit name /etc/systemd/system/juju-clean-shutdown.service is not valid.

Changed in cloud-init:
status: New → Incomplete
Revision history for this message
Ryan Beisner (1chb1n) wrote :

FYI, the issue I was hitting is a different one. Raised @ https://bugs.launchpad.net/juju-core/+bug/1488554. Thanks again.

Revision history for this message
Scott Moser (smoser) wrote :

i've pushed the fix. the cloud-init.log file is the key here. generally speaking, looking for WARN in cloud-init.log shows most issues.

Revision history for this message
Scott Moser (smoser) wrote :

not sure why this wasn't marked fix-released by 0.7.7~bzr1138-0ubuntu1 , but it should be fixed now.

Changed in cloud-init:
status: Incomplete → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.