<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body>
<div class="moz-cite-prefix">On 02/04/2016 08:49 AM, Oleg Fayans
wrote:<br>
</div>
<blockquote cite="mid:56B3029F.70001@redhat.com" type="cite">
<pre wrap="">Hi Petr,
On 02/03/2016 02:19 PM, Petr Spacek wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 3.2.2016 10:22, Oleg Fayans wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Guys, can anyone take a look at this?
</pre>
</blockquote>
<pre wrap="">
The commit message does not explain why you are setting search path.
</pre>
</blockquote>
<pre wrap="">
Fixed.
</pre>
<blockquote type="cite">
<pre wrap="">
I have to say that I do not like touching resolv.conf, as stated many times
earlier. Why the test has to reconfigure the host and cannot use values
provided by the provisioning system?
</pre>
</blockquote>
<pre wrap="">
This patch exactly removes this messing around with nameservers in
resolv.conf
It introduces the possibility to put ipa domain in the search directive
of resolv.conf so that we could test service autodiscovery during client
installation.
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
I just verified that the tampering with resolv.conf is not needed
(libvirt and ovirt/rhev). I think this is an artifact from the whole
issue of "let's use improvised domain names, what can go wrong"
approach that was uncovered by the enforced DNS checks. I think we
can defer the networking configuration to provisioning system.<br>
<br>
<pre class="moz-signature" cols="72">--
Milan Kubik</pre>
</body>
</html>