<div dir="ltr">Yes that would do it, thanks for the update :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 5:21 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>
all of the nodes that already made updates in the past have<br>
<br>
/etc/yum.repos.d/ovirt-4.1-pre<wbr>-dependencies.repo<br>
/etc/yum.repos.d/ovirt-4.1-pre<wbr>.repo<br>
<br>
i went through the logs in /var/log/ovirt-engine/host-dep<wbr>loy/ and my own notes and discovered/remembered that this being presented with RC versions started on 20170707 when i updated my nodes from 4.1.2 to 4.1.3-0.3.rc3.20170622082156.g<wbr>it47b4302 (!). probably there was a short timespan when you erroneously published a RC version in the wrong repo, my nodes "caught" it and dragged this along until today when i finally cared ;-) I moved the /etc/yum.repos.d/ovirt-4.1-pre<wbr>*.repo files away and now everything seems fine<br>
<br>
Regards<br>
Matthias<span class=""><br>
<br>
Am 2017-08-31 um 15:25 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>
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 ?<br>
<br>
Thanks,<br>
Yuval.<br>
<br></span><div><div class="h5">
On Thu, Aug 31, 2017 at 4:19 PM, 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>
thanks a lot.<br>
<br>
So i understand everything is fine with my nodes and i'll wait until<br>
the update GUI shows the right version to update (4.1.5 at the moment).<br>
<br>
Regards<br>
Matthias<br>
<br>
<br>
Am 2017-08-31 um 14:56 schrieb Yuval Turgeman:<br>
<br>
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<br>
new image-update rpm is published, yum update will pull those<br>
packages. So you have 1 system that was a fresh install and the<br>
others were upgrades.<br>
Next, the post install script for those image-update rpms will<br>
install --justdb the image-update rpms to the new image (so<br>
running yum update in the new image won't try to pull again the<br>
same version).<br>
<br>
Regarding the 4.1.6 it's very strange, we'll need to check the<br>
repos to see why it was published.<br>
<br>
As for nodectl, if there are no changes, it won't be updated and<br>
you'll see an "old" version or a version that doesn't seem to be<br>
matching the current image, but it is ok, we are thinking of<br>
changing its name to make it less confusing.<br>
<br>
Hope this helps,<br>
Yuval.<br>
<br>
<br>
On Thu, Aug 31, 2017 at 11:17 AM, Matthias Leopold<br>
<<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@meduniwien.a<wbr>c.at</a><br>
<mailto:<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@medun<wbr>iwien.ac.at</a>><br></div></div>
<mailto:<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@medun<wbr>iwien.ac.at</a><div><div class="h5"><br>
<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<br>
process<br>
and the involved rpm packages.<br>
<br>
We have 4 nodes, all running oVirt Node 4.1.3. Three of<br>
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-<wbr>4.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-<wbr>4.1.3-1.el7.centos.noarch',<br>
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<br>
'4.1.3-0.20170705.0.el7'. This<br>
node was the last one i installed and never made a version<br>
update<br>
before.<br>
<br>
I only began using oVirt starting with 4.1, but already<br>
completed<br>
minor version upgrades of oVirt nodes. IIRC this 'mysterious'<br>
ovirt-node-ng-image-update package comes into place when<br>
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?<br>
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>> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><span class=""><br>
<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>
<<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailm<wbr>an/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>
<br>
-- Matthias Leopold<br>
IT Systems & Communications<br>
Medizinische Universität Wien<br>
Spitalgasse 23 / BT 88 /Ebene 00<br>
A-1090 Wien<br></span>
Tel: <a href="tel:%2B43%201%2040160-21241" value="+4314016021241" target="_blank">+43 1 40160-21241</a> <tel:%2B43%201%2040160-21241><br>
Fax: <a href="tel:%2B43%201%2040160-921200" value="+43140160921200" target="_blank">+43 1 40160-921200</a> <tel:%2B43%201%2040160-921200><br>
<br>
<br>
</blockquote><div class="HOEnZb"><div class="h5">
<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>
</div></div></blockquote></div><br></div>