1:32 p.m.
This is a multi-part message in MIME format.
--------------EF578D2809121361A4CDCB0B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Can you try if these settings inside /etc/resolv.conf can make oVirt
engine web uo work better?
options rotate
options timeout:1
options attempts:1
Please note that nslookup and dig commands seem not to go through
these settings if you change them.
But if you use eg ping command you can see they work as expected (at
least the rotate one).
I could indeed, the issue I saw yesterday is resolved already. I was
merely thinking we might have a potential single point of failure here.
While the primary nameserver was offline the machine (where the
ovirt-engine is running) itself had no problem doing name-resolution,
still oVirt-ui was acting rather unpleasant.
And since my changes to resolv.conf only had an impact after restarting
the engine I thought there are some internals, such as a cache causing
this problem.
I can't say for sure if this was due to long delays, but some operations
in the UI, I was waiting for several minutes before cancelling. And I
believe that is more than enough time for the OS to try a second
nameserver.
But this could by all mean have something to do with my
infrastructure/setup. So let me do some more digging, and if I'm wrong,
my apologies for the noise.
Brgds,
Jonas
--------------EF578D2809121361A4CDCB0B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote
cite="mid:CAG2kNCzEvR9fR-xwrYxYooMEFV2EVvBYzgVZ=HE=oCObpucP-A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Can you try if these settings inside /etc/resolv.conf
can make oVirt engine web uo work better?</div>
<div><br>
</div>
<div>options rotate<br>
</div>
<div>options timeout:1</div>
<div>options attempts:1</div>
<div><br>
</div>
<div>Please note that nslookup and dig commands seem not to
go through these settings if you change them.</div>
<div>But if you use eg ping command you can see they work as
expected (at least the rotate one).</div>
<div><br>
</div>
<div> </div>
</div>
</div>
</div>
</blockquote>
I could indeed, the issue I saw yesterday is resolved already. I was
merely thinking we might have a potential single point of failure
here. <br>
While the primary nameserver was offline the machine (where the
ovirt-engine is running) itself had no problem doing
name-resolution, still oVirt-ui was acting rather unpleasant.<br>
And since my changes to resolv.conf only had an impact after
restarting the engine I thought there are some internals, such as a
cache causing this problem.<br>
<br>
I can't say for sure if this was due to long delays, but some
operations in the UI, I was waiting for several minutes before
cancelling. And I believe that is more than enough time for the OS
to try a second nameserver. <br>
<br>
But this could by all mean have something to do with my
infrastructure/setup. So let me do some more digging, and if I'm
wrong, my apologies for the noise.<br>
<br>
Brgds,<br>
Jonas<br>
</body>
</html>
--------------EF578D2809121361A4CDCB0B--