<div dir="ltr"><div>Hi Fernando, <br></div><br>There was a problem with the version you're using, the details can be found here [1].<br><br>Please try to use a newer release of node-ng-4.1 for the upgrade.<br><br><br>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1427468">https://bugzilla.redhat.com/show_bug.cgi?id=1427468</a><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 15, 2017 at 8:50 PM, FERNANDO FREDIANI <span dir="ltr"><<a href="mailto:fernando.frediani@upx.com" target="_blank">fernando.frediani@upx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Well, this failed badly.<br>
In another try it did the upgrade to the newer version it was not
being able to do before, but upon reboot several services fail to
start and the host doesn't come up. I then rebooted into the
previous version.<br>
</p>
<p>A complete re-install seems to be the only option.<br>
Seems the upgrade process need refining.</p>
<p>Taking the opportunity what is the procedure to remove from the
Engine a Host that will never come back up ? Seems the remove
option is grayed when the server is offline or unreachable.</p><span class="HOEnZb"><font color="#888888">
<p>Fernando<br>
</p></font></span><div><div class="h5">
<br>
<div class="m_7176404729484810152moz-cite-prefix">On 15/03/2017 10:06, FERNANDO FREDIANI
wrote:<br>
</div>
<blockquote type="cite">
<p>Find it attached Yuval.</p>
<p>Fernando</p>
<p><br>
</p>
<div class="m_7176404729484810152moz-cite-prefix">On 14/03/2017 18:21, Yuval Turgeman
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Adding Ryan, Fernando, can you please attach
/tmp/imgbased.log ?</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mar 13, 2017 2:43 PM, "FERNANDO
FREDIANI" <<a href="mailto:fernando.frediani@upx.com" target="_blank">fernando.frediani@upx.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">
<p>Hi Yedidyah.</p>
Running oVirt-Node <b>4.1.0--0.20170201.0+1</b> on the
nodes and tried a normal upgrade. It detected it has to
upgrade to <b>4.1.1-0.3.rc1.20170303133657.g<wbr>it20d3594.el7.centos</b>
from the ovirt-4.1-pre repository.
<p>The upgrade finished with the following problems:</p>
<p>...<br>
Running transaction<br>
Updating : ovirt-node-ng-image-4.1.1-0.3.<wbr>rc1.20170303133657.git20d3594.<wbr>el7.centos.noarch <wbr>
1/4 <br>
Updating : ovirt-node-ng-image-update-4.1<wbr>.1-0.3.rc1.20170303133657.git2<wbr>0d3594.el7.centos.noarch <wbr>
2/4 <br>
mount: special device /dev/onn_kvm01/ovirt-node-ng-4<wbr>.1.1-0.20170303.0+1
does not exist<br>
cp: target ‘/tmp/tmp.N6JgSdFcu6/usr/share<wbr>/imgbased/’
is not a directory<br>
rm: cannot remove ‘/tmp/tmp.N6JgSdFcu6/usr/share<wbr>/imgbased/*image-update*.rpm’:
No such file or directory<br>
umount: /tmp/tmp.N6JgSdFcu6: not mounted<br>
...</p>
<p>So it seems it was not able to do it correctly.<br>
This is the second time it happens and I had to remove
manually these packages containing 4.1.1 version.</p>
<p>Tried also:</p>
<p># lvdisplay | grep ovirt-node-ng-4.1.1-0.20170303<wbr>.0+1<br>
LV Path /dev/onn_kvm01/ovirt-node-ng-4<wbr>.1.1-0.20170303.0+1<br>
LV Name ovirt-node-ng-4.1.1-0.20170303<wbr>.0+1<br>
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4<wbr>.1.1-0.20170303.0+1<br>
fdisk: cannot open /dev/onn_kvm01/ovirt-node-ng-4<wbr>.1.1-0.20170303.0+1:
No such file or directory<br>
# vgchange -ay<br>
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4<wbr>.1.1-0.20170303.0+1
(then worked)</p>
But the upon reboot it came back to 4.1.0 as if 4.1.1
never existed<br>
<br>
Fernando<br>
<br>
<div class="m_7176404729484810152m_5957114426930454955moz-cite-prefix">On
12/03/2017 03:30, Yedidyah Bar David wrote:<br>
</div>
<blockquote type="cite">
<pre>On Fri, Mar 10, 2017 at 2:37 PM, FERNANDO FREDIANI
<a class="m_7176404729484810152m_5957114426930454955moz-txt-link-rfc2396E" href="mailto:fernando.frediani@upx.com" target="_blank"><fernando.frediani@upx.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>I am not sure if another email I sent went through but has anyone got
problems when upgrading a running oVirt-node-ng from 4.1.0 to 4.1.1.
</pre>
</blockquote>
<pre>What kind of problems?
</pre>
<blockquote type="cite">
<pre>Is the only solution a complete reinstall of the node ?
</pre>
</blockquote>
<pre>No, this should work.
Best,
</pre>
<blockquote type="cite">
<pre>Thanks
Fernando
______________________________<wbr>_________________
Users mailing list
<a class="m_7176404729484810152m_5957114426930454955moz-txt-link-abbreviated" href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a class="m_7176404729484810152m_5957114426930454955moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a>
</pre>
</blockquote>
<pre></pre>
</blockquote>
</div>
______________________________<wbr>_________________
Users mailing list
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a>
</blockquote></div></div>
</blockquote>
</blockquote>
</div></div></div></blockquote></div><br></div>