yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 18.3. 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: 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/1770462

Title:
  Allow empty stages

Status in cloud-init:
  Fix Released

Bug description:
  While users that modify the config file should remove any stages they
  do not want executed failing to do so results in a traceback:

  Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 638, in status_wrapper
      ret = functor(name, args)
    File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 416, in main_init
      return (init.datasource, run_module_section(mods, name, name))
    File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 107, in run_module_section
      (which_ran, failures) = mods.run_section(full_section_name)
    File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 817, in run_section
      raw_mods = self._read_modules(section_name)
    File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 700, in _read_modules
      for item in cfg_mods:
  TypeError: 'NoneType' object is not iterable

  Rather than complaining cloud-init should handle this gracefully and
  just skip the stage and do nothing.

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