<div dir="ltr">Hi,<div><br></div><div>oVirt node ng is shipped with a placeholder rpm preinstalled.</div><div>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).</div><div><br></div><div>Regarding the 4.1.6 it's very strange, we'll need to check the repos to see why it was published.</div><div><br></div><div>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.</div><div><br></div><div>Hope this helps,</div><div>Yuval.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 11:17 AM, 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>
i still don't completely understand the oVirt Node update process and the involved rpm packages.<br>
<br>
We have 4 nodes, all running oVirt Node 4.1.3. Three of them show as available updates 'ovirt-node-ng-image-update-4.<wbr>1.6-0.1.rc1.20170823083853.git<wbr>d646d2f.el7.centos' (i don't want run release candidates), one of them shows 'ovirt-node-ng-image-update-4.<wbr>1.5-1.el7.centos' (this is what i like). The node that doesn't want to upgrade to '4.1.6-0.1.rc1' lacks the rpm package 'ovirt-node-ng-image-update-4.<wbr>1.3-1.el7.centos.noarch', only has 'ovirt-node-ng-image-update-pl<wbr>aceholder-4.1.3-1.el7.centos.<wbr>noarch'. Also the version of ovirt-node-ng-nodectl is '4.1.3-0.20170709.0.el7' instead of '4.1.3-0.20170705.0.el7'. This node was the last one i installed and never made a version update before.<br>
<br>
I only began using oVirt starting with 4.1, but already completed minor version upgrades of oVirt nodes. IIRC this 'mysterious' ovirt-node-ng-image-update package comes into place when updating a node for the first time after initial installation. Usually i wouldn't care about all of this, but now i have this RC update situation that i don't want. How is this supposed to work? How can i resolve it?<br>
<br>
thx<br>
matthias<br>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<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>
</blockquote></div><br></div>