This bug was fixed in the package linux - 4.2.0-14.16
---------------
linux (4.2.0-14.16) wily; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1501818
* rebase to v4.2.2
* [Config] CONFIG_RTC_DRV_XGENE=y
- LP: #1499869
[ Upstream Kernel Changes ]
* mei: do not access freed cb in blocking write
- LP: #1494076
* mei: bus: fix drivers and devices names confusion
- LP: #1494076
* mei: bus: rename nfc.c to bus-fixup.c
- LP: #1494076
* mei: bus: move driver api functions at the start of the file
- LP: #1494076
* mei: bus: rename uevent handler to mei_cl_device_uevent
- LP: #1494076
* mei: bus: don't enable events implicitly in device enable
- LP: #1494076
* mei: bus: report if event registration failed
- LP: #1494076
* mei: bus: revamp device matching
- LP: #1494076
* mei: bus: revamp probe and remove functions
- LP: #1494076
* mei: bus: add reference to bus device in struct mei_cl_client
- LP: #1494076
* mei: bus: add me client device list infrastructure
- LP: #1494076
* mei: bus: enable running fixup routines before device registration
- LP: #1494076
* mei: bus: blacklist the nfc info client
- LP: #1494076
* mei: bus: blacklist clients by number of connections
- LP: #1494076
* mei: bus: simplify how we build nfc bus name
- LP: #1494076
* mei: bus: link client devices instead of host clients
- LP: #1494076
* mei: support for dynamic clients
- LP: #1494076
* mei: disconnect on connection request timeout
- LP: #1494076
* mei: define async notification hbm commands
- LP: #1494076
* mei: implement async notification hbm messages
- LP: #1494076
* mei: enable async event notifications only from hbm version 2.0
- LP: #1494076
* mei: add mei_cl_notify_request command
- LP: #1494076
* mei: add a handler that waits for notification on event
- LP: #1494076
* mei: add async event notification ioctls
- LP: #1494076
* mei: support polling for event notification
- LP: #1494076
* mei: implement fasync for event notification
- LP: #1494076
* mei: bus: add and call callback on notify event
- LP: #1494076
* mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED
- LP: #1494076
* mei: me: d0i3: add the control registers
- LP: #1494076
* mei: me: d0i3: add flag to indicate D0i3 support
- LP: #1494076
* mei: me: d0i3: enable d0i3 interrupts
- LP: #1494076
* mei: hbm: reorganize the power gating responses
- LP: #1494076
* mei: me: d0i3: add d0i3 enter/exit state machine
- LP: #1494076
* mei: me: d0i3: move mei_me_hw_reset down in the file
- LP: #1494076
* mei: me: d0i3: exit d0i3 on driver start and enter it on stop
- LP: #1494076
* mei: me: add sunrise point device ids
- LP: #1494076
* mei: hbm: bump supported HBM version to 2.0
- LP: #1494076
* mei: remove check on pm_runtime_active in __mei_cl_disconnect
- LP: #1494076
* mei: fix debugfs files leak on error path
- LP: #1494076
[ Upstream Kernel Changes ]
* rebase to v4.2.2
- LP: #1492132
-- Tim Gardner <tim.gard...@canonical.com> Tue, 29 Sep 2015 09:02:13
-0700
** Changed in: linux (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1499869
Title:
maas wily deployment to HP Proliant m400 arm64 server cartridge fails
Status in cloud-init:
Confirmed
Status in curtin:
New
Status in cloud-init package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Vivid:
Fix Committed
Status in cloud-init source package in Wily:
Fix Released
Status in linux source package in Wily:
Fix Released
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/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
