cloud-init apply_net_config_names doesn't grok v2 configs

Bug #1709715 reported by Ryan Harper on 2017-08-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Ryan Harper

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.

Related branches

Scott Moser (smoser) on 2018-01-25
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Ryan Harper (raharper)

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers