← Back to team overview

kernel-packages team mailing list archive

[Bug 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails


This bug was fixed in the package cloud-init - 0.7.7~bzr1147-0ubuntu1

cloud-init (0.7.7~bzr1147-0ubuntu1) wily; urgency=medium

  * New upstream snapshot.
    * MAAS: fix oauth when system clock is bad (LP: #1499869)

 -- Scott Moser <smoser@xxxxxxxxxx>  Tue, 29 Sep 2015 20:16:57 -0400

** Changed in: cloud-init (Ubuntu Wily)
       Status: New => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
Status in curtin:
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  In Progress
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Committed

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
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling '' failed [2427570/120s]: request error [HTTPConnectionPool(host='', 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 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 [''] 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: