Bug 1075665

Use the workaround in the dup.


Yaniv

*** This bug has been marked as a duplicate of bug 1065730 ***

(In reply to Yaniv Dary from comment #1)
> Use the workaround in the dup.
If you mean https://bugzilla.redhat.com/show_bug.cgi?id=1065730#c2 , I'm still unable to install reports with it. 

          Please confirm installation settings (OK, Cancel) [OK]: OK
[ INFO  ] Cleaning async tasks and compensations
[ INFO  ] Checking the Engine database consistency
[ INFO  ] Stage: Transaction setup
[ INFO  ] Stopping engine service
[ INFO  ] Stopping websocket-proxy service
[ INFO  ] Stage: Misc configuration
[ INFO  ] Stage: Package installation
[ INFO  ] Stage: Misc configuration
[ INFO  ] Creating PostgreSQL 'ovirt_engine_history' database
[ INFO  ] Configuring PostgreSQL
[ INFO  ] Creating PostgreSQL 'ovirt_engine_reports' database
[ INFO  ] Configuring PostgreSQL
[ INFO  ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20140312161544._oNgjx.sql'.
[ INFO  ] Updating Engine database schema
[ INFO  ] Creating DWH database schema
[ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory
[ INFO  ] Rolling back database schema
[ INFO  ] Clearing Engine database engine
[ INFO  ] Restoring Engine database engine
[ INFO  ] Rolling back DWH database schema
[ INFO  ] Clearing DWH database ovirt_engine_history
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140312161424.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

This is a different issue. Always attach logs and please note that you opened this bug on reports when the error was on dwh initially. 



Yaniv

this is the error:
otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.connection.Plugin._customization
2014-03-12 16:39:14 DEBUG otopi.ovirt_engine_setup.database database.execute:132 Database: 'ovirt_engine_history', Statement: '
                select count(*) as count
                from information_schema.tables
                where table_schema = 'public';
            ', args: {}
2014-03-12 16:39:14 DEBUG otopi.ovirt_engine_setup.database database.execute:137 Creating own connection
2014-03-12 16:39:14 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.connection connection._customization:286 database connection failed
Traceback (most recent call last):
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/db/connection.py", line 284, in _customization
    ] = dbovirtutils.isNewDatabase()
  File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/database.py", line 452, in isNewDatabase
    transaction=False,
  File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/database.py", line 159, in execute
    sslmode=sslmode,
OperationalError: FATAL:  password authentication failed for user "ovirt_engine_history"
FATAL:  password authentication failed for user "ovirt_engine_history"


AlonAny idea why it fails?


Yaniv

The log you attached doesn't match the error you posted. Please recheck this is the correct log.



Yaniv

Please wait for next build, or test with 3.4.0 master.

(In reply to Alon Bar-Lev from comment #8)
> Please wait for next build, or test with 3.4.0 master.

Will there be any related patch in next build?

(In reply to Petr Beňas from comment #10)
> (In reply to Alon Bar-Lev from comment #8)
> > Please wait for next build, or test with 3.4.0 master.
> 
> Will there be any related patch in next build?

There were significant changes in setup database access. If there are other issues we will fix on top.

Please test upgrade using av3 (run setup twice).
Closing for now and reopen if you hit this after this test.


Yaniv

I was able to upgrade to av3 from av2 with using the --offline parameter and saying "No" to reports and dwh installation. 

Then with re-running the rhevm-setup, I'm getting following yum error (not very well formatted thought). The error is gone when "--offline" parameter is used, but the setup does not ask for installing dwh and reports. 

Don't consider the difficult upgrade from av2 to av3 a problem, since it won't be performed by customers, but I see a real problem here in the failure to install the dwh and reports. 

If you claim it works for you, please provide exact steps how you managed to make it working. 

[ INFO  ] Checking for product updates...
[ ERROR ] Yum: [u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jbossas', 'rhevm-setup-plugin-ovirt-engine conflicts with rhevm-3.0.8_0001-1.el6_3.x86_64', u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jbossas-messaging', u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jakarta-commons-discovery >= 1:0.4-7', u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jbossas-ws-cxf']
[ INFO  ] Yum: Performing yum transaction rollback

(In reply to Petr Beňas from comment #13)
> I was able to upgrade to av3 from av2 with using the --offline parameter and
> saying "No" to reports and dwh installation. 
> 
> Then with re-running the rhevm-setup, I'm getting following yum error (not
> very well formatted thought). The error is gone when "--offline" parameter
> is used, but the setup does not ask for installing dwh and reports. 
> 
> Don't consider the difficult upgrade from av2 to av3 a problem, since it
> won't be performed by customers, but I see a real problem here in the
> failure to install the dwh and reports. 
> 
> If you claim it works for you, please provide exact steps how you managed to
> make it working. 
> 
> [ INFO  ] Checking for product updates...
> [ ERROR ] Yum: [u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires
> jbossas', 'rhevm-setup-plugin-ovirt-engine conflicts with
> rhevm-3.0.8_0001-1.el6_3.x86_64',
> u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jbossas-messaging',
> u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires
> jakarta-commons-discovery >= 1:0.4-7',
> u'rhevm-jboss-deps-3.0.8_0001-1.el6_3.x86_64 requires jbossas-ws-cxf']
> [ INFO  ] Yum: Performing yum transaction rollback

This is not related to history and reports and not to the topic. Open a separate bug.


Yaniv