yahoo-eng-team team mailing list archive

[Chad Smith <1852100@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 19.4. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
       Status: In Progress => 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/1852100

Title:
  Cloud-init fails if metadata local-hostname is null

Status in cloud-init:
  Fix Released

Bug description:
  If I run cloud-init with a config drive containing a metadata file
  which has local-hostname set to null, I get the following traceback:

  Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 447, in find_source
      if s.get_data():
    File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 132, in get_data
      self._get_standardized_metadata())
    File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 110, in _get_standardized_metadata
      'local-hostname': self.get_hostname(),
    File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 317, in get_hostname
      if util.is_ipv4(lhost):
    File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 544, in is_ipv4
      toks = instr.split('.')

  Tested on CentOS 7.7, cloud-init 18.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1852100/+subscriptions