[Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?

[Alon Bar-Lev]

----- Original Message -----
> From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "users" <users at ovirt.org>
> Sent: Sunday, April 6, 2014 3:43:09 PM
> Subject: Re: [Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?
> 
> On Sun, Apr 6, 2014 at 11:34 AM, Alon Bar-Lev <alonbl at redhat.com> wrote:
> 
> >
> > You need to remove and apply this[1] to fix that problem, I thought you
> > applied it.
> >
> > [1] http://gerrit.ovirt.org/#/c/25998/
> >
> >>
> >> Gianluca
> >>
> 
> Ah ok, right. I forgot that.
> Now all ended ok (see below)
> I see that now the user is defined into the db instead of palin file as in
> 3.3.

Great.

> How can I reset the password of ovirt-admin?
> (previously I used it only at certain times and watched the clear text file
> /usr/share/ovirt-engine-reports/reports/users/ovirt-002dadmin.xml
> I forgot it ;-)

I think you can run:

# engine-setup --otopi-environment="OVESETUP_REPORTS_CONFIG/adminPassword=str:<password>"

Or interactively:

# engine-setup --otopi-environment="OVESETUP_REPORTS_CONFIG/adminPassword=none:"

> so that I can try and check previous data?
> At the end of the e-mail what I wrote as a summary and if right I can
> add into release notes...

Well, better to wait for 3.4.1 I think.

> 
> after first tun of engine-setup, that updates only engine itself you have to:
> 
> 1) yum update
> and you will get
> ovirt-engine-dwh-3.4.0-2.fc19.noarch
> ovirt-engine-reports-3.4.0-2.fc19.noarch
> 
> and also these 2 new packages installed
> ovirt-engine-dwh-setup-3.4.0-2.fc19.noarch
> ovirt-engine-reports-setup-3.4.0-2.fc19.noarch
> 
> 2) patch as from
> http://gerrit.ovirt.org/#/c/26118/
> and
> http://gerrit.ovirt.org/#/c/25998/
> 
> 3) engine-setup
> (no more ovirt-engine-dwh-setup and ovirt-engine-reports-setup to run)
> 
> And if you have run 3) before 2) you have to remove the directory tree under
> /var/lib/ovirt-engine-reports/build-conf
> and run 2) and 3) again
> due to currently targeted for 3.4.1 bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1084749

Thank you for your help!

Alon.