7:37 a.m.
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.
Is the only solution a complete reinstall of the node ?
Thanks
Fernando
1:30 a.m.
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
--
Didi
8:42 a.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--
9 a.m.
On Mon, Mar 13, 2017 at 2:42 PM, FERNANDO FREDIANI
<fernando.frediani(a)upx.com> wrote:
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.
I think 4.1-pre should include a later version. Did you try again recently?
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
...
Looks to me like [1], which should be fixed in 4.1.1 (and in current 4.1-pre).
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1427082
Best,
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
--
Didi
5:21 p.m.
Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ?
On Mar 13, 2017 2:43 PM, "FERNANDO FREDIANI" <fernando.frediani(a)upx.com>
wrote:
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>
<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 listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:06 a.m.
Find it attached Yuval.
Fernando
On 14/03/2017 18:21, Yuval Turgeman wrote:
Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ?
On Mar 13, 2017 2:43 PM, "FERNANDO FREDIANI"
<fernando.frediani(a)upx.com <mailto:fernando.frediani@upx.com>> wrote:
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> <mailto:fernando.frediani@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 <mailto:Users@ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>
>
_______________________________________________ Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
2:50 p.m.
This is a multi-part message in MIME format.
--------------2B005FDF882FAE4A6C7D7F8A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Well, this failed badly.
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.
A complete re-install seems to be the only option.
Seems the upgrade process need refining.
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.
Fernando
On 15/03/2017 10:06, FERNANDO FREDIANI wrote:
Find it attached Yuval.
Fernando
On 14/03/2017 18:21, Yuval Turgeman wrote:
> Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ?
>
> On Mar 13, 2017 2:43 PM, "FERNANDO FREDIANI"
> <fernando.frediani(a)upx.com <mailto:fernando.frediani@upx.com>> wrote:
>
> 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> <mailto:fernando.frediani@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 <mailto:Users@ovirt.org>
>>> http://lists.ovirt.org/mailman/listinfo/users
>>> <http://lists.ovirt.org/mailman/listinfo/users>
> _______________________________________________ Users mailing
> list Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
> <http://lists.ovirt.org/mailman/listinfo/users>
>
--------------2B005FDF882FAE4A6C7D7F8A
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>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>
<p>Fernando<br>
</p>
<br>
<div class="moz-cite-prefix">On 15/03/2017 10:06, FERNANDO FREDIANI
wrote:<br>
</div>
<blockquote cite="mid:629efbf0-3b90-1380-68d4-6f26219b48df@upx.com"
type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<p>Find it attached Yuval.</p>
<p>Fernando</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 14/03/2017 18:21, Yuval Turgeman
wrote:<br>
</div>
<blockquote
cite="mid:CAGDbUeeqqB=Bk=bd7fg_G8AUFbOrWb7-0hb_JFqKegrQo96rmQ@mail.gmail.com"
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 moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com">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.<wbr>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.<wbr>rc1.20170303133657.git20d3594.<wbr>el7.centos.noarch <wbr>
1/4 <br>
Updating :
ovirt-node-ng-image-update-4.<wbr>1.1-0.3.rc1.20170303133657.<wbr>git20d3594.el7.centos.noarch <wbr>
2/4 <br>
mount: special device
/dev/onn_kvm01/ovirt-node-ng-<wbr>4.1.1-0.20170303.0+1
does not exist<br>
cp: target ‘/tmp/tmp.N6JgSdFcu6/usr/<wbr>share/imgbased/’
is not a directory<br>
rm: cannot remove
‘/tmp/tmp.N6JgSdFcu6/usr/<wbr>share/imgbased/*image-update*.<wbr>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.<wbr>20170303.0+1<br>
LV Path
/dev/onn_kvm01/ovirt-node-ng-<wbr>4.1.1-0.20170303.0+1<br>
LV Name
ovirt-node-ng-4.1.1-0.<wbr>20170303.0+1<br>
# fdisk -l
/dev/onn_kvm01/ovirt-node-ng-<wbr>4.1.1-0.20170303.0+1<br>
fdisk: cannot open
/dev/onn_kvm01/ovirt-node-ng-<wbr>4.1.1-0.20170303.0+1:
No such file or directory<br>
# vgchange -ay<br>
# fdisk -l /dev/onn_kvm01/ovirt-node-ng-<wbr>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="m_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 moz-do-not-send="true"
class="m_5957114426930454955moz-txt-link-rfc2396E"
href="mailto:fernando.frediani@upx.com"
target="_blank">&lt;fernando.frediani(a)upx.com&gt;</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 moz-do-not-send="true"
class="m_5957114426930454955moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a>
<a moz-do-not-send="true"
class="m_5957114426930454955moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/<wbr>mailman/li...
</pre>
</blockquote>
<pre>
</pre>
</blockquote>
</div>
______________________________<wbr>_________________
Users mailing list
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer"
target="_blank">http://lists.ovirt.org/<wbr>mailman/li...
</blockquote></div></div>
</blockquote>
</blockquote>
</body></html>
--------------2B005FDF882FAE4A6C7D7F8A--
4:42 a.m.
Hi Fernando,
There was a problem with the version you're using, the details can be found
here [1].
Please try to use a newer release of node-ng-4.1 for the upgrade.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1427468
On Wed, Mar 15, 2017 at 8:50 PM, FERNANDO FREDIANI <
fernando.frediani(a)upx.com> wrote:
Well, this failed badly.
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.
A complete re-install seems to be the only option.
Seems the upgrade process need refining.
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.
Fernando
On 15/03/2017 10:06, FERNANDO FREDIANI wrote:
Find it attached Yuval.
Fernando
On 14/03/2017 18:21, Yuval Turgeman wrote:
Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ?
On Mar 13, 2017 2:43 PM, "FERNANDO FREDIANI" <fernando.frediani(a)upx.com>
wrote:
> 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>
<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 listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________ Users mailing list
> Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users
2836
days inactive
2846
days old
7 comments
3 participants
participants (3)
-
FERNANDO FREDIANI -
Yedidyah Bar David -
Yuval Turgeman