[Users] How to scratch previous versions reports and dwh installation?

Yedidyah Bar David didi at redhat.com
Sun Feb 2 14:34:38 UTC 2014


----- Original Message -----
> From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> To: "users" <users at ovirt.org>
> Sent: Sunday, February 2, 2014 3:56:25 PM
> Subject: [Users] How to scratch previous versions reports and dwh	installation?
> 
> Hello,
> I have some problems, I think they are also due to PosgreSQL access
> rules changes from f18 to f19.
> In particular if one has passed from fedora 18 to Fedora 19 and form
> 3.2 to 3.3 as I did; see
>  https://bugzilla.redhat.com/show_bug.cgi?id=1009335
> 
> Right now I have a problem with my AIO installation where trying to
> upgrade from 3.3.2 to 3.3.3 I got many problems related to RDBMS.

Is this related to dwh/reports?

> 
> Is there a way to completely get rid of prevous installtion and
> reinstall cleanly in 3.3.3 as I did on another system without getting
> problems.

So you want to delete dwh/reports only or also the engine?

> 
> I tried removing packages:
> yum remove ovirt-engine-dwh ovirt-engine-reports
> 
> and deleting related databases:
> 
> drop database ovirt_engine_history;
> drop database ovirtenginereports;

This might not be enough. Sadly there is currently no cleanup tool for
dwh/reports, similar to engine-cleanup for the engine.

For things to delete look at
/etc/ovirt*dwh* /etc/ovirt-*reports* /etc/ovirt-engine/*dwh* /etc/ovirt-engine/*reports*
/var/lib/ovirt-engine/deployments/*reports*

> 
> But then trying to install again packages and runnign setup I get this in
> log:
> 
> 2014-01-30 00:37:30::DEBUG::common_utils::446::root:: running sql
> query on host: localhost, port: 5432, db: ovirt_engine_history, user:
> engine, query: 'select 1 from history_configuration;'.
> 2014-01-30 00:37:30::DEBUG::common_utils::907::root:: Executing
> command --> '/usr/bin/psql --pset=tuples_only=on --set ON_ERROR_STOP=1
> --dbname ovirt_engine_history --host localhost --port 5432 --username
> engine -w -c select 1 from history_configuration;' in working
> directory '/root'
> 2014-01-30 00:37:30::DEBUG::common_utils::962::root:: output =
> 2014-01-30 00:37:30::DEBUG::common_utils::963::root:: stderr = ERROR:
> relation "history_configuration" does not exist
> LINE 1: select 1 from history_configuration;

This in itself is not necessarily a problem, unless of course setup failed
immediately after that.

Which versions of relevant packages? Can you please post full logs?

> 
> 
> Can anyone tell if I have to run any other purge operation, suche as
> any users or table on engine db itself?

IIRC nothing in the engine db itself. Didn't check that, though.

> And also what would be the expected configuration of
> /var/lib/pgsql/data/pg_hba.conf

Manually-edited? On a remote database server? Or local, letting the
setup programs edit it for you? Please post it if you have a specific
problem that you think might be related.

> and eventually
> /var/lib/pgsql/data/postgresql.conf

Only max_connections is edited by setup, to be 150. For a remote database you
want to change listen_addresses.

> for a fedora 19 system so that a setup for reports and dwh could complete?

In general, on a clean system, with a local database, the setup programs should
do what's needed and no manual fixes are needed.

Do note that, as Yaniv mentioned earlier, 3.3.3 should be used when released.
3.3.3-beta might probably be good enough if you can't wait.

Regards,
-- 
Didi



More information about the Users mailing list