<p dir="ltr">I could really use some help on this one. My efforts to debug VDSM via instrumenting the python code are not working - the compiled code must be cached somehow.</p>
<p dir="ltr">Something is wrong with the way the multipathd service is being restarted. It doesn't look too me that systemctl is even being called for it.</p>
<p dir="ltr">Thanks,<br>
Bob</p>
<div class="gmail_quote">On May 13, 2014 1:12 PM, "Bob Doolittle" <<a href="mailto:bob@doolittle.us.com">bob@doolittle.us.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Maybe this isn't the actual problem after all.<br>
<br>
I replaced /sbin/multipath with a script runs the old version, but
the suppresses those errors and returns exit status 0.<br>
But "vdsm-tool service-reload multipathd" is still failing and I
don't know why.<br>
<br>
I have attached my vdsm.log file.<br>
<br>
Any guidance appreciated. I'll try digging through the python code
for service.py and see if I can catch it when the multipath
configuration is in place to see the exact issue.<br>
<br>
-Bob<br>
<br>
<div>On 05/13/2014 12:27 PM, Bob Doolittle
wrote:<br>
</div>
<blockquote type="cite">
Hi,<br>
<br>
I have started a new installation as specified in the 3.4.1
release notes (fresh Fedora 19 install, yum localinstall <a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm" target="_blank">http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm</a>).<br>
<br>
This is failing in the step "Configuring the management bridge".<br>
<br>
Based on the vdsm.log, it appears I am hitting:<br>
<div>
<div> </div>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=988995" target="_blank"><b>Bug 988995</b></a>
-<span> <span>vdsm multipath.py restarts
mutipathd, cutting the branch vdsm sits on</span></span><br>
<br>
"multipath -F" is returning "invalid keyword: getuid_callout"
and it appears that this is causing vdsm-tool to abort (although
the command exit status is 0 and the bug report says that those
are only harmless warnings).<br>
</div>
<br>
There is no workaround stated in that bug report.<br>
<br>
Help?<br>
<br>
-Bob<br>
<br>
</blockquote>
<br>
</div>
</blockquote></div>