<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 10/01/2015 11:23 AM, Martin Basti wrote: </div> <blockquote cite="mid:560CFB9D.4070503@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 10/01/2015 10:18 AM, Milan Kubík wrote: </div> <blockquote cite="mid:560CEC50.6080707@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 10/01/2015 10:06 AM, Milan Kubík wrote: </div> <blockquote cite="mid:560CE96E.1000200@redhat.com" type="cite">Fixes <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://fedorahosted.org/freeipa/ticket/5331">https://fedorahosted.org/freeipa/ticket/5331</a> Patch attached. <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> Patch for ipa-4-2 branch. Milan <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> NACK <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://fpaste.org/273499/43691381/">http://fpaste.org/273499/43691381/</a> </blockquote> I disagree. From [1]: Fedora now by default relies on NetworkManager for network configuration. This is the case also for minimal installations and server installations. The cloud image, which you are probably using does not have NetworkManager installed. I think we can rely on the default here and assume NetworkManager is present. If you and the list disagree, I will make the fix depend on NetworkManager's presence. Nitpick: there can be other services that manage (and rewrite) resolv.conf. [1]: <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Tools/NetworkManager">https://fedoraproject.org/wiki/Tools/NetworkManager</a> <pre class="moz-signature" cols="72">-- Milan Kubik</pre> </body> </html>