[19:46] <nrezinorn> what populates netcfg ? it seems to be a merger of what a system has configured already and what cloud-init has in its datasource.  running into an issue where its trying to parse 'loopback' and fails to set up eth0
[19:48] <nrezinorn> temp fixed by adding an extra elif  line to handle the subnet_type == 'loopback', and that works so far.  the issue after that is that the default gateway is not being set in the ifcfg-eth0 file
[19:48] <nrezinorn> any ideas on where to look / how to fix it "proper"
[20:46] <smoser> nrezinorn, its quite possible it doesnt "clean" the old state out well.
[20:46] <smoser> that code path can be largely unit tested i think.
[20:47] <smoser> to let you play more quickly
[21:00] <mdorman> “can be largely unit tested” meaning the tests don’t exist at this point?
[21:03] <mdorman> what we did as a quick fix was just added a conditional for subnet_type == ‘loopback’ with a pass here:  https://git.launchpad.net/cloud-init/tree/cloudinit/net/sysconfig.py#n222   although i’m not totally clear why cloud-init is (re)configuring the lo interface in the first place.
[21:04] <mdorman> so not clear to me if what we did to fix this is appropriate or not
[21:05] <mdorman> didn’t have a chance to look at it any further today but can probably pick back up next week
[21:21] <smoser> mdorman, no.. is tested, just meaning you can modify the unit tests to do it.
[21:22] <mdorman> gottcha