This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1499869
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1499869
Title:
maas wily deployment to HP Proliant m400 arm64 server cartridge fails
Status in cloud-init:
New
Status in curtin:
New
Status in MAAS:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Vivid:
New
Status in linux source package in Wily:
Incomplete
Bug description:
This is the error seen on the console:
[ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]:
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
[ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 -
url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[2427570/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 0x7f7faa4b70>, 'Connection to 169.254.169.254 timed out. (connect
timeout=50.0)'))]
[ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 -
DataSourceEc2.py[CRITICAL]: Giving up on md from
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
[ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 -
url_helper.py[WARNING]: Calling 'http://<internal
ip>/latest/meta-data/instance-id' failed [0/120s]: bad status code [404]
This times out eventually and the node is left at the login prompt. I
can install wily via netboot without issue and some time back, wily
was deployable to this node from MAAS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
