This bug is believed to be fixed in cloud-init in 18.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: Confirmed => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.

  cloud-init apply_net_config_names doesn't grok v2 configs

Status in cloud-init:
  Fix Released

Bug description:
  when supplying cloud-init with a network-configuration in version:2
  format, the rename code doesn't find any of the set-name parameters as
  the function expects a v1 config format.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to