[Users] engine reports and dwh setup in 3.3.2

[Gianluca Cecchi]

On Fri, Jan 17, 2014 at 11:50 AM, Sandro Bonazzola  wrote:

>
> This has been fixed yesterday http://gerrit.ovirt.org/#/c/23304/
>


Please note that at the end of the problem, only PostgreSQL database
has been restarted, while ovirt engine kept stopped as for the
requested input at the beginning of install.
Should be better at least ask/notify the user ?

 systemctl status ovirt-engine
ovirt-engine.service - oVirt Engine
   Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled)
   Active: inactive (dead) since Fri 2014-01-17 11:20:33 CET; 25min ago
 Main PID: 14918 (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/ovirt-engine.service

Jan 17 11:02:16 myengine.mydomain systemd[1]: Starting oVirt Engine...
Jan 17 11:02:16 myengine.mydomain systemd[1]: Started oVirt Engine.
Jan 17 11:02:16 myengine.mydomain ovirt-engine.py[14918]: 2014-01-17
11:02:16,886 ovirt-engine: WARNING _setupEngineApps:...nored
Jan 17 11:20:32 myengine.mydomain systemd[1]: Stopping oVirt Engine...
Jan 17 11:20:33 myengine.mydomain systemd[1]: Stopped oVirt Engine.

In my case restart of engine gives errors and unable to startup
correctly: started from a systemctl point of view but not able to
login to web admin gui

In engine log:
2014-01-17 11:47:36,929 ERROR
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-4) [7909477c] Timer update run
timeinfo failed. Exception:: java.lang.IllegalStateException:
JBAS011049: Component is stopped
        at org.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:104)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Fi
nal]
        at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:127)
[jboss-as-ee-7.1.1.Final.jar:7.1
.1.Final]
        at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116)
[jboss-as-ejb3-7.1
.1.Final.jar:7.1.1.Final]
        at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentIn
stanceAssociationInterceptor.java:48)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:211)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:363)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:194)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation.jar:1.1.1.Final]
        at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation.jar:1.1.1.Final]


Anyway I applied the patch to
/usr/share/ovirt-engine-reports/ovirt-engine-reports-setup.py and then
successfully reexecuted
ovirt-engine-reports-setup ;-)

# ovirt-engine-reports-setup
Welcome to ovirt-engine-reports setup utility
Backing up reports DB...                              [ DONE ]
Updating Redirect Servlet...                          [ DONE ]
Importing reports...                                  [ DONE ]
Customizing Server...                                 [ DONE ]
Running post setup steps...                           [ DONE ]
Starting ovirt-engine...                              [ DONE ]
Restarting httpd...                                   [ DONE ]
Succesfully installed ovirt-engine-reports.

engine web admin available and reportsportal  too
but the password set up during first broken install for ovirt-admin
user doesn't work

Invalid credentials supplied.

Could not login to JasperReports Server.

Any hints on how to solve? Manually change in Postgres?

NOTES:
- keep an eye about ovirt-engine not restarted after reports setup
error, not a good thing IMHO
- in patched file I see some lines above "logging.debug("Imporing
users")" without the "t"
So when it happens to further modify the file you can put this type fix too...
- in main reports page if you click on "Need help logging in?" link,
the pop-up says "rhevm-admin" instead of what setup specified as
"ovirt-admin" (none of these logins works:
(Please choose a password for the reports admin user(s) (ovirt-admin): )

Gianluca