<div dir="ltr">Hi,<div><br></div><div>Don't quite understand how you got to that 4.1.6 rc, it's only available in the pre release repo, can you paste the yum repos that are enabled on your system ?</div><div><br></div><div>Thanks,</div><div>Yuval.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 4:19 PM, Matthias Leopold <span dir="ltr"><<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@meduniwien.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
thanks a lot.<br>
<br>
So i understand everything is fine with my nodes and i'll wait until the update GUI shows the right version to update (4.1.5 at the moment).<br>
<br>
Regards<br>
Matthias<span class=""><br>
<br>
<br>
Am 2017-08-31 um 14:56 schrieb Yuval Turgeman:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Hi,<br>
<br>
oVirt node ng is shipped with a placeholder rpm preinstalled.<br>
The image-update rpms obsolete the placeholder rpm, so once a new image-update rpm is published, yum update will pull those packages. So you have 1 system that was a fresh install and the others were upgrades.<br>
Next, the post install script for those image-update rpms will install --justdb the image-update rpms to the new image (so running yum update in the new image won't try to pull again the same version).<br>
<br>
Regarding the 4.1.6 it's very strange, we'll need to check the repos to see why it was published.<br>
<br>
As for nodectl, if there are no changes, it won't be updated and you'll see an "old" version or a version that doesn't seem to be matching the current image, but it is ok, we are thinking of changing its name to make it less confusing.<br>
<br>
Hope this helps,<br>
Yuval.<br>
<br>
<br></span><div><div class="h5">
On Thu, Aug 31, 2017 at 11:17 AM, Matthias Leopold <<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@meduniwien.a<wbr>c.at</a> <mailto:<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@medun<wbr>iwien.ac.at</a>>> wrote:<br>
<br>
hi,<br>
<br>
i still don't completely understand the oVirt Node update process<br>
and the involved rpm packages.<br>
<br>
We have 4 nodes, all running oVirt Node 4.1.3. Three of them show as<br>
available updates<br>
'ovirt-node-ng-image-update-4.<wbr>1.6-0.1.rc1.20170823083853.git<wbr>d646d2f.el7.centos'<br>
(i don't want run release candidates), one of them shows<br>
'ovirt-node-ng-image-update-4.<wbr>1.5-1.el7.centos' (this is what i<br>
like). The node that doesn't want to upgrade to '4.1.6-0.1.rc1'<br>
lacks the rpm package<br>
'ovirt-node-ng-image-update-4.<wbr>1.3-1.el7.centos.noarch', only has<br>
'ovirt-node-ng-image-update-pl<wbr>aceholder-4.1.3-1.el7.centos.<wbr>noarch'.<br>
Also the version of ovirt-node-ng-nodectl is<br>
'4.1.3-0.20170709.0.el7' instead of '4.1.3-0.20170705.0.el7'. This<br>
node was the last one i installed and never made a version update<br>
before.<br>
<br>
I only began using oVirt starting with 4.1, but already completed<br>
minor version upgrades of oVirt nodes. IIRC this 'mysterious'<br>
ovirt-node-ng-image-update package comes into place when updating a<br>
node for the first time after initial installation. Usually i<br>
wouldn't care about all of this, but now i have this RC update<br>
situation that i don't want. How is this supposed to work? How can i<br>
resolve it?<br>
<br>
thx<br>
matthias<br>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br></div></div>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailma<wbr>n/listinfo/users</a>><br>
<br>
<br><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
-- <br>
Matthias Leopold<br>
IT Systems & Communications<br>
Medizinische Universität Wien<br>
Spitalgasse 23 / BT 88 /Ebene 00<br>
A-1090 Wien<br>
Tel: <a href="tel:%2B43%201%2040160-21241" value="+4314016021241" target="_blank">+43 1 40160-21241</a><br>
Fax: <a href="tel:%2B43%201%2040160-921200" value="+43140160921200" target="_blank">+43 1 40160-921200</a><br>
</font></span></blockquote></div><br></div>