cloud-init-dev team mailing list archive

[Ryan Harper <ryan.harper@xxxxxxxxxxxxx>]

On Fri, Mar 17, 2017 at 10:14 AM, Scott Moser <smoser@xxxxxxxxxx> wrote:

> So as it is here we're not writing that file (ifcfg-lo), and I think that
> is sane.
> we just assume that that is there and present, if not, it kind of falls in
> the range of "broken image"?  that sound reasonable ?
>

Yes, except that there are network paths in the distro/rhel.py which *do*
write an ifcfg-lo;

If you read an eni which has a lo, then the net_convert creates an lo entry
and it will get written out.



>
>
>
> --
> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-
> init/+merge/319943
> Your team cloud init development team is requested to review the proposed
> merge of ~smoser/cloud-init:bug/net-explicit-lo-type into
> cloud-init:master.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cloud-init-dev
> Post to     : cloud-init-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cloud-init-dev
> More help   : https://help.launchpad.net/ListHelp
>

-- 
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/319943
Your team cloud init development team is requested to review the proposed merge of ~smoser/cloud-init:bug/net-explicit-lo-type into cloud-init:master.