This bug is believed to be fixed in cloud-init in 17.1. 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/1715738
Title:
Cloud config modules are not skipped based on distro support
Status in cloud-init:
Fix Released
Bug description:
cloudinit.stages emits logs messages like the following when the
cloudconfig module's distro attribute doesn't match the running
disribution
When a cloudinit.config.cc*py module distros attribute doesn't match
the discovered Distribution.name, cloudinit.stages emits a log message
about skipping the module in the following form:
2017-09-07 06:03:25,838 - stages.py[INFO]: Skipping modules ['runcmd']
because they are not verified on distro 'ubuntu'. To run anyway, add
them to 'unverified_modules' in config.
But, it doesn't actually skip running the module, we can see in the logging
that follows:
Running module runcmd (<module 'cloudinit.config.cc_runcmd' from
'/usr/lib/python3/dist-packages/cloudinit/config/cc_runcmd.py'>) with frequency
once-per-instance.
cloudinit.stages should honor a skipped module and avoid running its
handler.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1715738/+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
