2:42 p.m.
This is a multi-part message in MIME format.
--------------47A66F4C176EC0923C0633B5
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi Yedidyah.
Running oVirt-Node *4.1.0--0.20170201.0+1* on the nodes and tried a
normal upgrade. It detected it has to upgrade to
*4.1.1-0.3.rc1.20170303133657.git20d3594.el7.centos* from the
ovirt-4.1-pre repository.
The upgrade finished with the following problems:
...
Running transaction
Updating :
ovirt-node-ng-image-4.1.1-0.3.rc1.20170303133657.git20d3594.el7.centos.noarch
1/4
Updating :
ovirt-node-ng-image-update-4.1.1-0.3.rc1.20170303133657.git20d3594.el7.centos.noarch
2/4
mount: special device /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1
does not exist
cp: target ‘/tmp/tmp.N6JgSdFcu6/usr/share/imgbased/’ is not a directory
rm: cannot remove
‘/tmp/tmp.N6JgSdFcu6/usr/share/imgbased/*image-update*.rpm’: No such
file or directory
umount: /tmp/tmp.N6JgSdFcu6: not mounted
...
So it seems it was not able to do it correctly.
This is the second time it happens and I had to remove manually these
packages containing 4.1.1 version.
Tried also:
# lvdisplay | grep ovirt-node-ng-4.1.1-0.20170303.0+1
LV Path /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1
LV Name ovirt-node-ng-4.1.1-0.20170303.0+1
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1
fdisk: cannot open /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1: No
such file or directory
# vgchange -ay
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1 (then worked)
But the upon reboot it came back to 4.1.0 as if 4.1.1 never existed
Fernando
On 12/03/2017 03:30, Yedidyah Bar David wrote:
On Fri, Mar 10, 2017 at 2:37 PM, FERNANDO FREDIANI
<fernando.frediani(a)upx.com> wrote:
> 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.
What kind of problems?
> Is the only solution a complete reinstall of the node ?
No, this should work.
Best,
> Thanks
>
> Fernando
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
--------------47A66F4C176EC0923C0633B5
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">
<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.git20d3594.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.rc1.20170303133657.git20d3594.el7.centos.noarch
1/4 <br>
Updating :
ovirt-node-ng-image-update-4.1.1-0.3.rc1.20170303133657.git20d3594.el7.centos.noarch
2/4 <br>
mount: special device
/dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1 does not exist<br>
cp: target ‘/tmp/tmp.N6JgSdFcu6/usr/share/imgbased/’ is not a
directory<br>
rm: cannot remove
‘/tmp/tmp.N6JgSdFcu6/usr/share/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.0+1<br>
LV Path
/dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1<br>
LV Name ovirt-node-ng-4.1.1-0.20170303.0+1<br>
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1<br>
fdisk: cannot open
/dev/onn_kvm01/ovirt-node-ng-4.1.1-0.20170303.0+1: No such file or
directory<br>
# vgchange -ay<br>
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-4.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="moz-cite-prefix">On 12/03/2017 03:30, Yedidyah Bar David
wrote:<br>
</div>
<blockquote
cite="mid:CAHRwYXst-5oaV0Z+LEHHAx8m25zoEq8_K6BKT58nfa4hJkm1iA@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Mar 10, 2017 at 2:37 PM, FERNANDO FREDIANI
<a class="moz-txt-link-rfc2396E"
href="mailto:fernando.frediani@upx.com"><fernando.frediani@upx.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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 wrap="">
What kind of problems?
</pre>
<blockquote type="cite">
<pre wrap="">
Is the only solution a complete reinstall of the node ?
</pre>
</blockquote>
<pre wrap="">
No, this should work.
Best,
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks
Fernando
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>
--------------47A66F4C176EC0923C0633B5--