<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 27, 2017 at 6:32 PM, Juan Hernández <span dir="ltr">&lt;<a href="mailto:jhernand@redhat.com" target="_blank">jhernand@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">That is a known issue:<br>
<br>
  fence_rhevm can only work as RHEV admin user not a regular user (that<br>
requires &quot;Filter: true http header)<br>
  <a href="https://bugzilla.redhat.com/1287059" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>1287059</a><br>
<br>
That was fixed in fence-agents-4.0.11-47.el7, but I guess it wasn&#39;t<br>
backported to CentOS 6.<br>
<br>
I&#39;d suggest that you open a bug for this component in the Red Hat<br>
Enterprise Linux bug tracker, requesting that the fix be back-ported.<br>
<br>
Meanwhile, if you are in a hurry, you can take the CentOS 7 fence_rhev<br>
script, which should work.<br>
<br>
You will most likely also need to add --ssl-indecure to the command line<br>
of the agent, because you will most likely be using the default self<br>
signed certificate authority used by the engine.<br>
<br>
Note that the latest version of this script uses the &#39;Filter: true&#39;<br>
header to drop privileges. That means that even when using<br>
&#39;admin@internal&#39; you have to make sure that &#39;admin@internal&#39; has<br>
permissions for the VM that you want to fence, otherwise it will not be<br>
able to find/fence it.<br>
</blockquote></div><br></div><div class="gmail_extra">Thanks for the feedback Juan.<br></div><div class="gmail_extra">I confirm that using fence_rhevm from latest CentOS 7 version it worked.<br></div><div class="gmail_extra">These were the lines in my cluster.conf<br></div><div class="gmail_extra"><br><pre class="gmail-screen">                &lt;clusternode name=&quot;p2viclnorasvi1&quot; nodeid=&quot;1&quot; votes=&quot;1&quot;&gt;<br>                        &lt;fence&gt;<br>                                &lt;method name=&quot;1&quot;&gt;<br>                                        &lt;device name=&quot;ovirt_fencedelay&quot; port=&quot;p2vorasvi1&quot;/&gt;<br>                                &lt;/method&gt;<br>                        &lt;/fence&gt;<br>                &lt;/clusternode&gt;<br>                &lt;clusternode name=&quot;p2viclnorasvi2&quot; nodeid=&quot;2&quot; votes=&quot;1&quot;&gt;<br>                        &lt;fence&gt;<br>                                &lt;method name=&quot;1&quot;&gt;<br>                                        &lt;device name=&quot;ovirt_fence&quot; port=&quot;p2vorasvi2&quot;/&gt;<br>                                &lt;/method&gt;<br>                        &lt;/fence&gt;<br>                &lt;/clusternode&gt;<br>        &lt;/clusternodes&gt;<br>        &lt;quorumd label=&quot;p2vcluorasvi&quot; votes=&quot;1&quot;&gt;<br>                &lt;heuristic interval=&quot;2&quot; program=&quot;ping -c1 -w1 172.16.10.231&quot; score=&quot;1&quot; tko=&quot;200&quot;/&gt;<br>        &lt;/quorumd&gt;<br>        &lt;fencedevices&gt;<br>                &lt;fencedevice agent=&quot;fence_rhevm&quot; delay=&quot;30&quot; ipaddr=&quot;10.4.192.43&quot; login=&quot;g.cecchi@internal&quot; passwd_script=&quot;/usr/local/bin/pwd_dracnode01.sh&quot; name=&quot;ovirt_fencedelay&quot; ssl=&quot;on&quot; ssl_insecure=&quot;on&quot; shell_timeout=&quot;20&quot; power_wait=&quot;10&quot;/&gt;<br>                &lt;fencedevice agent=&quot;fence_rhevm&quot; ipaddr=&quot;10.4.192.43&quot; login=&quot;g.cecchi@internal&quot; passwd_script=&quot;/usr/local/bin/pwd_dracnode02.sh&quot; name=&quot;ovirt_fence&quot; ssl=&quot;on&quot; ssl_insecure=&quot;on&quot; shell_timeout=&quot;20&quot; power_wait=&quot;10&quot;/&gt;<br>        &lt;/fencedevices&gt;<br><br><span style="font-family:arial,helvetica,sans-serif">Using admin@internal didn&#39;t work even if I set the permissions at vm level too...<br></span></pre><pre class="gmail-screen"><span style="font-family:arial,helvetica,sans-serif">It worked with my username (g.cecchi) that has SuperUser system privilege and also at VM level.<br></span></pre><pre class="gmail-screen"><span style="font-family:arial,helvetica,sans-serif">Is it yet necessary to have a user with SuperUser privilege at system level?<br></span></pre><pre class="gmail-screen"><span style="font-family:arial,helvetica,sans-serif">Tomorrow (today... ;-) I&#39;m going to open a bugzilla to backport the feature.<br></span></pre><pre class="gmail-screen"><span style="font-family:arial,helvetica,sans-serif">Thanks again,<br>Gianluca<br></span></pre></div></div>