Vivid: DataSourceCloudSigma.py[WARNING]: failed to get hypervisor product name via dmi data

Bug #1427263 reported by Brad Figg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

The current Vivid MAAS install image does not install. After getting the warning specified in the bug title it goes on to:
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 ConnecctTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f8f6699b38>, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))]

Note, other series install just fine. The issue is only with the most recent Vivid image.

This is preventing testing of Vivid kernels from happening.

Related branches

Brad Figg (brad-figg)
Changed in cloud-init (Ubuntu):
importance: Undecided → Critical
description: updated
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Cause is that any instance that returns dmi data will be flags as running on CloudSIgma:

From cloudinit/sources/DataSourceCloudSigma.py
 45 def is_running_in_cloudsigma(self):
 46 """
 47 Uses dmi data to detect if this instance of cloud-init is running
 48 in the CloudSigma's infrastructure.
 49 """
 50 uname_arch = os.uname()[4]
 51 if uname_arch.startswith("arm") or uname_arch == "aarch64":
 52 # Disabling because dmi data on ARM processors
 53 LOG.debug("Disabling CloudSigma datasource on arm (LP: #1243287)")
 54 return False
 55
 56 LOG.debug("determining hypervisor product name via dmi data")
 57 sys_product_name = util.read_dmi_data("system-product-name")
 58 if not sys_product_name:
 59 LOG.warn("failed to get hypervisor product name via dmi data")
 60 return False
 61 else:
 62 LOG.debug("detected hypervisor as {}".format(sys_product_name))
 63 return 'cloudsigma' in sys_product_name.lower()
 64
 65 LOG.warn("failed to query dmi data for system product name")
 66 return False

Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Scratch the prior comment. My analysis is incorrect.

Brad can you get /var/log/cloud* and /var/lib/cloud?

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

ben, this is fallout of python3.
My work-in-progress is at lp:~smoser/cloud-ilp1427263
the maas datasource is busted in [at least] 2 ways
a.) get_cmdline_url() was broken (fixed that)
b.) oauthlib doesn't seem to be working right
http://paste.ubuntu.com/10506162/

$ dpkg-query --show python3-oauthlib
python3-oauthlib 0.6.1-1
$ python3 -c 'import oauthlib; oauthlib.oauth1.Client("foo", client_secret="foo_bar")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: 'module' object has no attribute 'oauth1'

the use of oauthlib is as described in https://oauthlib.readthedocs.org/en/latest/oauth1/client.html

Changed in cloud-init (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Scott Moser (smoser) wrote :

i'll have to finish this tomorrow,
but given 'patch-image' at http://paste.ubuntu.com/10507095/
and the deb attached, we'r emuch closer.

Revision history for this message
Dan Watkins (oddbloke) wrote :

https://bugs.launchpad.net/cloud-init/+bug/1427687 is probably also related to this issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
cloud-init (0.7.7~bzr1072-0ubuntu1) vivid; urgency=medium

  * d/control: move software-properties-common to Recommends
    this helps reduce snappy builds
  * New upstream snapshot.
    * fix MAAS datasource (LP: #1427263)
 -- Scott Moser <email address hidden> Tue, 03 Mar 2015 20:46:41 -0500

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
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.