[ovirt-users] oVirt Node 4.1.2 offering RC update?
Vinícius Ferrão
ferrao at if.ufrj.br
Sun Jul 9 17:10:46 UTC 2017
Thanks Lev!
It’s already showing up here:
Installing:
ovirt-node-ng-image-update noarch 4.1.3-1.el7.centos ovirt-4.1 550 M
replacing ovirt-node-ng-image-update-placeholder.noarch 4.1.2-1.el7.centos
Updating:
ovirt-engine-appliance noarch 4.1-20170622.1.el7.centos ovirt-4.1 967 M
V.
On 9 Jul 2017, at 13:26, Lev Veyde <lveyde at redhat.com<mailto:lveyde at redhat.com>> wrote:
Hi Vinicius,
It's actually due to my mistake, and as result the package got tagged with the RC version instead of the GA.
The package itself was based on the 4.1.3 code, though.
I rebuilt it and published a fixed package, so the issue should be resolved now.
Thanks in advance,
On Sat, Jul 8, 2017 at 5:12 AM, Vinícius Ferrão <ferrao at if.ufrj.br<mailto:ferrao at if.ufrj.br>> wrote:
Hello,
I’ve noted a strange thing on oVirt. On the Hosted Engine an update was offered and I was a bit confused, since I’m running the latest oVirt Node release.
To check if 4.1.3 was already released I issued an “yum update” on the command line and for my surprise an RC release was offered. This not seems to be right:
======================================================================================================================
Package Arch Version Repository Size
======================================================================================================================
Installing:
ovirt-node-ng-image-update noarch 4.1.3-0.3.rc3.20170622082156.git47b4302.el7.centos ovirt-4.1 544 M
replacing ovirt-node-ng-image-update-placeholder.noarch 4.1.2-1.el7.centos
Updating:
ovirt-engine-appliance noarch 4.1-20170622.1.el7.centos ovirt-4.1 967 M
Transaction Summary
======================================================================================================================
Install 1 Package
Upgrade 1 Package
Total download size: 1.5 G
Is this ok [y/d/N]: N
Is this normal behavior? This isn’t really good, since it can lead to stable to unstable moves on production. If this is normal, how can we avoid it?
Thanks,
V.
_______________________________________________
Users mailing list
Users at ovirt.org<mailto:Users at ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
--
Lev Veyde
Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com/>
lev at redhat.com<mailto:lev at redhat.com> | lveyde at redhat.com<mailto:lveyde at redhat.com>
[https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png]<https://red.ht/sig>
TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170709/004fd275/attachment-0001.html>
More information about the Users
mailing list