[ovirt-users] Upgrade from 3.5rc to 3.5 final question

[Sandro Bonazzola]

Il 27/10/2014 16:58, Gianluca Cecchi ha scritto:
> I see this in release notes for 3.5:
> "
> If you're using pre-release repo you'll need to re-enable pre release
> repository:
> 
> [ovirt-3.5-pre]
> name=Latest oVirt 3.5 Pre Release
> #baseurl=http://resources.ovirt.org/pub/ovirt-3.5-pre/rpm/fc$releasever/
> mirrorlist=
> http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-3.5-pre-fc$releasever
> enabled=1
> skip_if_unavailable=1
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-3.5
> 
> and to run:
> 
>     # yum update "ovirt-engine-setup*"
>     # engine-setup
> "
> 
> but this leaves me some doubts...
> I currently have RC3 (or 4, I don't remember exactly).
> But if I walk through the pre-repo mirror, it seems to me that for example
> I will get
> 
> ovirt-engine-backend-3.5.0.1-0.0.master.20141009085636.el6.noarch.rpm
> 
> while going through 3.5 repo I will get
> ovirt-engine-backend-3.5.0.1-1.el6.noarch.rpm
> 
> Are they indeed the same?
> 
> Can you confirm that if I have a RC release I still have to use -pre repo
> to update to official 3.5.0?

ovirt-engine-backend-3.5.0.1-1 is ovirt-engine-3.5.0.1_rc5 (ovirt-engine-backend-3.5.0.1-0.0.master.20141009085636)
plus the following patches:
* 0aa366e - (tag: ovirt-engine-3.5.0.1) build: ovirt-engine-3.5.0.1 (2 weeks ago) <Sandro Bonazzola>
* 7b1335a - core: dont copy old num of sockets on hotplug (2 weeks ago) <Omer Frenkel>
* b23106c - core, engine: Fix VM CD change in JSON RPC (2 weeks ago) <Vitor de Lima>

Using the -pre repo allow you to rollback rpms if something goes wrong during the upgrade process.
You can avoid to add -pre repo, but then you won't have rollback support during the upgrade.



> 
> Thanks,
> Gianluca
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com