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(a)redhat.com&gt; wrote: 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. ovirtenginereports=# select * from jiuser; id | username | tenantid | fullname | emailaddress | password | externallydefined | enable d | previouspasswordchangetime -----+---------------+----------+------------------+--------------+----------------------------------+-------------------+------- --+---------------------------- 5 | jasperadmin | 1 | jasperadmin User | | 349AFAADD5C5A2BD477309618DCD58B9 | f | f | 2013-10-17 00:58:10.01 6 | anonymousUser | 1 | anonymousUser | | CF35D2E88192D6EB | f | f | 2013-10-17 00:58:10.346 129 | ovirt-admin | 1 | ovirt-admin | | D41B13B925B503A13CF5EBB35EB9BFF7 | f | t | 130 | admin | 1 | admin | | 5C598ADA6CCE35AA | f | f | (4 rows) 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 ;-) ) 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... ... Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Cleaning async tasks and compensations [ INFO ] Checking the Engine database consistency [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping dwh service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20140406140343.eSKtje.sql'. [ INFO ] Updating Engine database schema [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20140406140401.A6N4NM.sql'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Regenerating Jasper's build configuration files [ INFO ] Exporting data out of Jasper [ INFO ] Backing up database localhost:ovirtenginereports to '/var/lib/ovirt-engine-reports/backups/reports-20140406140547.a7FquY.sql'. [ INFO ] Deploying Jasper [ INFO ] Importing data into Jasper [ INFO ] Configuring Jasper Java resources [ INFO ] Configuring Jasper Database resources [ INFO ] Customizing Jasper [ INFO ] Customizing Jasper metadata [ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up --== SUMMARY ==-- SSH fingerprint: FE:C6:E1:DE:5D:44:DC:30:CB:12:A3:F7:01:3A:49:83 Internal CA 55:D5:F1:1F:1A:65:45:61:D5:17:A5:74:36:84:65:3B:E5:53:6E:84 Web access is enabled at: http://tekkaman.localdomain.local:80/ovirt-engine https://tekkaman.localdomain.local:443/ovirt-engine --== END OF SUMMARY ==-- [ INFO ] Starting engine service [ INFO ] Restarting httpd [ INFO ] Restarting nfs services [ INFO ] Starting dwh service [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140406140949-setup.conf' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140406140253.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully The workflow for upgrade from configured 3.3 dwh and reports should be this Coming from a 3.3.4 with dwh and reports already configured, in my case I start with ovirt-engine-dwh-3.3.4-1.fc19.noarch ovirt-engine-reports-3.3.4-1.fc19.noarch 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 Gianluca