[Users] Wondering about updating ovirt from 3.0 to 3.1

[Steve Gordon]

----- Original Message -----
> From: "Ofer Schreiber" <oschreib at redhat.com>
> To: "Jason Brooks" <jbrooks at redhat.com>
> Cc: users at ovirt.org
> Sent: Tuesday, July 24, 2012 7:13:32 AM
> Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
> 
> 
> 
> ----- Original Message -----
> > On 07/12/2012 06:08 PM, Robert Middleswarth wrote:
> > > On 07/12/2012 03:01 PM, Dominic Kaiser wrote:
> > >> So does Fedora 16 have an Ovirt 3.1 repo?  It seems best way to
> > >> do
> > >> this correct me if I am wrong:
> > > No.  There are no Fedora 16 Repo's
> > >>
> > >> 1. Uninstall 3.0
> > >> 2. engine-cleanup do not drop database
> > >> 3. Reinstall
> > >>
> > >> Good to go right?  Will this mess with vm's already running etc.
> > > Pretty certain this will break things badly.
> > >
> > > The un-test but the way that should work is.
> > >
> > > Uninstall oVirt 3.0 do not engine-clean
> > > Upgrade from Fedora 16 to Fedora 17.
> > > Add the beta repo's
> > > yum clean all
> > > Yum install ovirt-engine
> > > Run enginue-upgrade and follow it instructions
> 
> I'm afraid this won't work, we changed so many things in the
> packaging/setup between 3.0 and 3.1
> 
> > 
> > 
> > Has anyone else tested this? I just tried it on a test rig of F16
> > running 3.0, upgrading to 3.1 beta on F17. All the steps completed
> > fine,
> > except that I had to remove ovirt-engine-jbossas, which conflicted
> > with
> > the new, from Fedora, jboss-as, before installing ovirt-engine 3.1.
> > 
> > After engine-upgrade completed, I wasn't able to access the engine.
> > Jboss-as was stopped, as was httpd. Starting them up didn't make
> > the
> > engine accessible, though. I just got the default fedora pages for
> > JBoss
> > and for Apache.
> > 
> > On my own oVirt setup, I moved from 3.0 to 3.1 by moving my VMs and
> > templates to my export domain, detaching my export and iso domains,
> > and
> > installing 3.1 from scratch, before importing my iso and export
> > domains
> > and ferrying my VMs and templates over to my new data domain.
> > 
> > What's the most sane upgrade advice we can offer to oVirt 3.0
> > users?
> > 
> > Jason
> 
> the "sane" upgrade path (nothing is sane in Fedora 16 to Fedora 17
> upgrade):
> 1. run engine-cleanup, do not drop DB
> 2. remove all ovirt-engine rpms (including the JBoss one)
>   - please not that this will remove the PKI, so you'll have to
>   re-install your hosts
> 3. Do the fedora upgrade
> 4. install ovirt-engine rpms
> 5. run engine-setup
>   - Give same passwords to the DB/admin user
> 
> in this case, engine-setup should upgrade the db, and not install it.
> we didn't tried this approach yet, so I'll appreciate any input.

Can someone please try this out and verify it works? I'd like to include this process in the release notes.

Thanks,

Steve