[Users] engine reports and dwh setup in 3.3.2
Hello, I have some questions regarding wheat in subject fro 3.3.2. In November I upgraded my AIO install from fc18 3.2.3 to fc19 3.3.1 following: http://www.ovirt.org/OVirt_3.2_to_3.3_upgrade All went ok. In Fc18 reports and DWH worked ok if I rememebr correctly. Probably in November I didn't run any setup again for dwh and reports... after upgrade This is a test/home server Today I updated to 3.3.2 without problems and tried upgrade of dwh and reports too. One problem I found is that upgrading from f18 to f19, now my postgres user cannot directly connect to db without password. I see that my pg_hba.conf is now this way local all all md5 host ovirtenginereports engine_reports 0.0.0.0/0 md5 host ovirtenginereports engine_reports ::0/0 md5 host all all 127.0.0.1/32 md5 host all all ::1/128 md5 so that running ovirt-engine-dwh-setup aborted because of db connections such as 2013-12-21 14:27:47::DEBUG::common_utils::908::root:: retcode = 0 2013-12-21 14:27:47::DEBUG::common_utils::864::root:: Executing command --> '/bin/su -l postgres -c /usr/bin/psql -U postgres -d template1 -tAc "select 1;"' in working directory '/root' 2013-12-21 14:27:47::DEBUG::common_utils::906::root:: output = 2013-12-21 14:27:47::DEBUG::common_utils::907::root:: stderr = Password for user postgres: psql: fe_sendauth: no password supplied I temporarily solved putting this entry for unix domains local access in my pg-hba.conf and restarting the db service local all postgres trust and dwh setup completed ok with this ouptut below where I see a possible bug in the initial username request But what if a fresh install? Would the setup give the same error for default fc19 restricted postgres setup? Also, It asks me if I want to create it and instead of asking the username it suddenly outputs an error also at first input But then it asks the username again and all goes well. The first request shouldn't give error... [root@tekkaman ~]# ovirt-engine-dwh-setup Welcome to ovirt-engine-dwh setup utility This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes Error: user name cannot be empty Provide a username for read-only user : ovirt_ruser Provide a password for read-only user: Warning: Weak Password. Re-type password: Should postgresql be setup with secure connection? (yes|no): yes Existing DB was found on the system. The size of the detected DB is 27 MB, free space in the backup folder /var/lib/ovirt-engine/backups is approximately 10.0 GB. The upgrade utility can backup the existing database. The time and space required for the database backup depend on its size. The detected DB size is 27 MB. This process takes time, and in some cases (for instance, when the size is few GBs) may take few hours to complete. Would you like to continue and backup the existing database? Answering "no" will skip the backup step and continue the upgrade without backing up the database (yes|no): yes Are you sure you would like to continue and backup database ovirt_engine_history? Answering "no" will stop the upgrade (yes|no): yes Backing up the DB... [ DONE ] Upgrade DB... [ DONE ] Creating read-only user... [ DONE ] Setting DB connectivity... [ DONE ] Starting ovirt-engine... [ DONE ] Starting oVirt-ETL... [ DONE ] Successfully installed ovirt-engine-dwh. The installation log file is available at: /var/log/ovirt-engine/ovirt-engine-dwh-setup-2013_12_21_14_56_37.log The DB was backed up as '/var/lib/ovirt-engine/backups/ovirt-engine-history.backup.2013_12_21_14_58_21' The DB backup was created with compression. You must use "pg_restore" command if you need to recover the DB from the backup. For reports setup I got instead this kind of error in war deploy [root@tekkaman ~]# ovirt-engine-reports-setup Welcome to ovirt-engine-reports setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Editing XML files... [ DONE ] Setting DB connectivity... [ DONE ] Exporting scheduled reports... [ DONE ] Exporting current users... [ DONE ] Deploying Server... [ ERROR ] Failed step import-minimal-ce of JasperReports Server Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2013_12_21_14_59_36.log and in log [advanced-sql] Executing resource: /usr/share/jasperreports-server/buildomatic/install_resources/sql/postgresql/quartz.ddl [advanced-sql] 0 rows affected [advanced-sql] 5 of 153 SQL statements executed successfully BUILD SUCCESSFUL Total time: 2 seconds 2013-12-21 15:00:23::DEBUG::common_utils::1028::root:: stderr = [advanced-sql] Failed to execute: create table JIAccessEvent ( id int8 not null, user_id int8 not null, event_date timestamp not null, resource_id int8 not null, updating bool not null, primary key (id) ) [advanced-sql] org.postgresql.util.PSQLException: ERROR: relation "jiaccessevent" already exists I uploaded both dwh and reports logs dwh see the zip of various attempts and engine.log here https://drive.google.com/file/d/0BwoPbcrMv8mvcHcxRDRpSUNpQXM/edit?usp=sharin... for reports: https://drive.google.com/file/d/0BwoPbcrMv8mvUWJmS1dFbTU1cTA/edit?usp=sharin... The problem is that now, without the reports war, if I try to run setup for the engine again I get: --== CONFIGURATION PREVIEW ==-- Database name : engine Database secured connection : False Database host : localhost Database user name : engine Database host name validation : False Datbase port : 5432 NFS setup : True NFS mount point : /ISO Firewall manager : iptables Configure WebSocket Proxy : True Host FQDN : tekkaman.localdomain.local Set application as default page : True Configure Apache SSL : False [ INFO ] Backing up database to '/var/lib/ovirt-engine/backups/engine-20131221151714.ttpGbB.sql'. [ INFO ] Updating database schema [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/var/lib/ovirt-engine/deployments/ovirt-engine-reports.war' [ INFO ] Yum Performing yum transaction rollback [ INFO ] Rolling back database schema [ INFO ] Clearing database engine [ INFO ] Restoring database engine [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131221151617.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of upgrade failed see log here: https://drive.google.com/file/d/0BwoPbcrMv8mveklYRjZSck9mSm8/edit?usp=sharin... BTW: note the cosmetical bug of mmisprinting the word "Database" in port numebr line Datbase port : 5432 ANy input to solve reports and engine-setup problem appreciated. On thing I noticed about dhw is that in /etc/ovirt-engine/ovirt-engine-dwh I have [root@tekkaman ovirt-engine-dwh]# ll total 8 -rw-rw----. 1 root root 1373 Dec 21 14:58 Default.properties -rw-rw----. 1 ovirt ovirt 1052 Oct 17 18:16 Default.properties.rpmnew [root@tekkaman ovirt-engine-dwh]# diff Default.properties Default.properties.rpmnew 7c7 < ovirtEngineHistoryDbUser=engine_history ---
ovirtEngineHistoryDbUser=postgres 9c9 < ovirtEngineHistoryDbPassword=0489TGUU
ovirtEngineHistoryDbPassword= 17c17 < ovirtEngineDbUser=engine
ovirtEngineDbUser=postgres 19,27c19 < ovirtEngineDbPassword=passw0rd < < #Connection Definition to Engine Health Status Portal < ## Connection Protocol (SSL or Unencrypted) < ovirtEnginePortalConnectionProtocol=https < ## Portal Address (JBoss' Location) < ovirtEnginePortalAddress=tekkaman.localdomain.local < ## Portal Port (JBoss' Port) < ovirtEnginePortalPort=443
ovirtEngineDbPassword= 43d34 < etlVersion=3.3.2
the password lines were encrypted during upgrade; previously there was plain password. And also etlVersion that contained 3.2 now contains current version So I presume it wwent ok Gianluca
Hello, as my past data are not important, is there at least any way to start from scratch with Dwh and Reports, reinitializing my current situation? Is it as simple as drop the two databases ovirtenginereports and ovirt_engine_history or are there any other steps to perform? Thanks in advance, Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "users" <users@ovirt.org> Sent: Tuesday, December 24, 2013 3:46:08 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
Hello, as my past data are not important, is there at least any way to start from scratch with Dwh and Reports, reinitializing my current situation? Is it as simple as drop the two databases ovirtenginereports and ovirt_engine_history or are there any other steps to perform?
Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available. Yaniv
Thanks in advance, Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote:
Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available.
Ok, I'll wait good news about these items Just a question: when you write about blockers, are you referring to updates only or also to new setups directly made in 3.3.2 environments? thanks in advance, Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Yaniv Dary" <ydary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Saturday, January 4, 2014 12:59:46 AM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote:
Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available.
Ok, I'll wait good news about these items Just a question: when you write about blockers, are you referring to updates only or also to new setups directly made in 3.3.2 environments?
Local fresh installs should work and upgrades\remote fresh install will not probably.
thanks in advance, Gianluca
The oVirt 3.3.3 release should be working for all install and upgrade flows. Please use that on your setup once it's released. Yaniv ----- Original Message -----
From: "Yaniv Dary" <ydary@redhat.com> To: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, January 5, 2014 3:54:40 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Yaniv Dary" <ydary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Saturday, January 4, 2014 12:59:46 AM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote:
Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available.
Ok, I'll wait good news about these items Just a question: when you write about blockers, are you referring to updates only or also to new setups directly made in 3.3.2 environments?
Local fresh installs should work and upgrades\remote fresh install will not probably.
thanks in advance, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Jan 16, 2014 at 4:57 PM, Yaniv Dary wrote:
The oVirt 3.3.3 release should be working for all install and upgrade flows. Please use that on your setup once it's released.
I have just updated another infra (not all-in-one) from 3.3.2 to 3.3.3.beta1. It is an environment on f19. One engine + 2 hosts There are currently no reports/dwh installed at all Can I go with install/test or do I have to wait rc and/or final 3.3.3? If I can go, can I use https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua... as a workflow input? (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh) Let me know so that I can try Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Yaniv Dary" <ydary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Thursday, January 16, 2014 6:19:57 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Thu, Jan 16, 2014 at 4:57 PM, Yaniv Dary wrote:
The oVirt 3.3.3 release should be working for all install and upgrade flows. Please use that on your setup once it's released.
I have just updated another infra (not all-in-one) from 3.3.2 to 3.3.3.beta1. It is an environment on f19. One engine + 2 hosts There are currently no reports/dwh installed at all Can I go with install/test or do I have to wait rc and/or final 3.3.3?
I think a this point it is safe to install.
If I can go, can I use https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua...
as a workflow input? (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh)
You can try it, but not sure everything will be applicable.
Let me know so that I can try
Gianluca
On Thu, Jan 16, 2014 at 5:55 PM, Yaniv Dary wrote:
I think a this point it is safe to install.
If I can go, can I use https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua...
as a workflow input? (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh)
You can try it, but not sure everything will be applicable.
Let me know so that I can try
Gianluca
dwh part went ok and ovirt_engine_history db was created. The reports part got error # ovirt-engine-reports-setup Welcome to ovirt-engine-reports setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Editing XML files... [ DONE ] Setting DB connectivity... [ DONE ] Please choose a password for the reports admin user(s) (ovirt-admin): Warning: Weak Password. Retype password: Warning: Weak Password. Deploying Server... [ DONE ] Updating Redirect Servlet... [ DONE ] Importing reports... [ DONE ] Customizing Server... [ DONE ] global name 'preserveReportsJobs' is not defined Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2014_01_17_11_20_29.log It seems the main point in log file, as in standard output is this: 2014-01-17 11:22:22::ERROR::ovirt-engine-reports-setup::1196::root:: Failed to complete the setup of the reports package! 2014-01-17 11:22:22::DEBUG::ovirt-engine-reports-setup::1197::root:: Traceback (most recent call last): File "/bin/ovirt-engine-reports-setup", line 1163, in main if preserveReportsJobs: NameError: global name 'preserveReportsJobs' is not defined Let me know if you need full logs or if this is sufficient to debug code and propose a solution to try then again. Gianluca
Il 17/01/2014 11:40, Gianluca Cecchi ha scritto:
On Thu, Jan 16, 2014 at 5:55 PM, Yaniv Dary wrote:
I think a this point it is safe to install.
If I can go, can I use https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua...
as a workflow input? (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh)
You can try it, but not sure everything will be applicable.
Let me know so that I can try
Gianluca
dwh part went ok and ovirt_engine_history db was created.
The reports part got error
# ovirt-engine-reports-setup Welcome to ovirt-engine-reports setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Editing XML files... [ DONE ] Setting DB connectivity... [ DONE ] Please choose a password for the reports admin user(s) (ovirt-admin): Warning: Weak Password. Retype password: Warning: Weak Password. Deploying Server... [ DONE ] Updating Redirect Servlet... [ DONE ] Importing reports... [ DONE ] Customizing Server... [ DONE ] global name 'preserveReportsJobs' is not defined Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2014_01_17_11_20_29.log
It seems the main point in log file, as in standard output is this:
2014-01-17 11:22:22::ERROR::ovirt-engine-reports-setup::1196::root:: Failed to complete the setup of the reports package! 2014-01-17 11:22:22::DEBUG::ovirt-engine-reports-setup::1197::root:: Traceback (most recent call last): File "/bin/ovirt-engine-reports-setup", line 1163, in main if preserveReportsJobs: NameError: global name 'preserveReportsJobs' is not defined
This has been fixed yesterday http://gerrit.ovirt.org/#/c/23304/
Let me know if you need full logs or if this is sufficient to debug code and propose a solution to try then again.
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
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
On Fri, Jan 17, 2014 at 12:10 PM, Gianluca Cecchi wrote:
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?
Ok, digging into /bin/ovirt-engine-reports-setup I see that actually the password is written in clear text inside file /usr/share/ovirt-engine-reports/reports/users/ovirt-002dadmin.xml Not a great security choice, also because the file is currently readable by everyone on the system (and "rpm -qVv" doesn't complain about its permissions). I was then able to connect to reports portal and to see some output reports... Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Yaniv Dary" <ydary@redhat.com>, "users" <users@ovirt.org> Sent: Saturday, January 18, 2014 12:32:36 AM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Fri, Jan 17, 2014 at 12:10 PM, Gianluca Cecchi wrote:
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?
Ok, digging into /bin/ovirt-engine-reports-setup I see that actually the password is written in clear text inside file /usr/share/ovirt-engine-reports/reports/users/ovirt-002dadmin.xml
This was only due to setup failing in the middle, this is improved in 3.4 and you won't see that anymore.
Not a great security choice, also because the file is currently readable by everyone on the system (and "rpm -qVv" doesn't complain about its permissions). I was then able to connect to reports portal and to see some output reports...
Gianluca
On Sun, Jan 26, 2014 at 4:29 PM, Yaniv Dary wrote:
----- Original Message -----
From: "Gianluca Cecchi"
[snip]
Ok, digging into /bin/ovirt-engine-reports-setup I see that actually the password is written in clear text inside file /usr/share/ovirt-engine-reports/reports/users/ovirt-002dadmin.xml
This was only due to setup failing in the middle, this is improved in 3.4 and you won't see that anymore.
Not a great security choice, also because the file is currently readable by everyone on the system (and "rpm -qVv" doesn't complain about its permissions). I was then able to connect to reports portal and to see some output reports...
Gianluca
Ok. see also my NOTES from the previous e-mail about possible improvements: Thanks Gianluca " 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): ) "
On 01/17/2014 12:50 PM, Sandro Bonazzola wrote:
Il 17/01/2014 11:40, Gianluca Cecchi ha scritto:
On Thu, Jan 16, 2014 at 5:55 PM, Yaniv Dary wrote:
I think a this point it is safe to install.
If I can go, can I use https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua...
as a workflow input? (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh)
You can try it, but not sure everything will be applicable.
Let me know so that I can try
Gianluca
dwh part went ok and ovirt_engine_history db was created.
The reports part got error
# ovirt-engine-reports-setup Welcome to ovirt-engine-reports setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Editing XML files... [ DONE ] Setting DB connectivity... [ DONE ] Please choose a password for the reports admin user(s) (ovirt-admin): Warning: Weak Password. Retype password: Warning: Weak Password. Deploying Server... [ DONE ] Updating Redirect Servlet... [ DONE ] Importing reports... [ DONE ] Customizing Server... [ DONE ] global name 'preserveReportsJobs' is not defined Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2014_01_17_11_20_29.log
It seems the main point in log file, as in standard output is this:
2014-01-17 11:22:22::ERROR::ovirt-engine-reports-setup::1196::root:: Failed to complete the setup of the reports package! 2014-01-17 11:22:22::DEBUG::ovirt-engine-reports-setup::1197::root:: Traceback (most recent call last): File "/bin/ovirt-engine-reports-setup", line 1163, in main if preserveReportsJobs: NameError: global name 'preserveReportsJobs' is not defined
This has been fixed yesterday http://gerrit.ovirt.org/#/c/23304/
this is only merged in master. yaniv - which version is going to 3.3.3 - the otopi one?
Let me know if you need full logs or if this is sufficient to debug code and propose a solution to try then again.
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Jan 16, 2014 at 4:57 PM, Yaniv Dary wrote:
The oVirt 3.3.3 release should be working for all install and upgrade flows. Please use that on your setup once it's released.
Yaniv
----- Original Message -----
From: "Yaniv Dary" <ydary@redhat.com> To: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Cc: "users" <users@ovirt.org> Sent: Sunday, January 5, 2014 3:54:40 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Yaniv Dary" <ydary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Saturday, January 4, 2014 12:59:46 AM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote:
Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available.
Ok, I'll wait good news about these items Just a question: when you write about blockers, are you referring to updates only or also to new setups directly made in 3.3.2 environments?
Local fresh installs should work and upgrades\remote fresh install will not probably.
thanks in advance, Gianluca
Just to note that on my oVirt 3.3.2-1 allinone on fedora 19, after enabling updates-testing I get the same failure using 3.3.3rc [root@tekkaman ~]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-aio.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140129214203.log Version: otopi-1.1.2 (otopi-1.1.2-1.fc19) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization --== PACKAGES ==-- [ INFO ] Checking for product updates... Setup has found updates for some packages, do you wish to update them now? (Yes, No) [Yes]: [ INFO ] Checking for an update for Setup... --== NETWORK CONFIGURATION ==-- [WARNING] Failed to resolve tekkaman.localdomain.local using DNS, it can be resolved only locally Setup can automatically configure the firewall on this system. Note: automatic configuration of the firewall may overwrite current settings. Do you want Setup to configure the firewall? (Yes, No) [Yes]: [ INFO ] iptables will be configured as firewall manager. --== DATABASE CONFIGURATION ==-- --== OVIRT ENGINE CONFIGURATION ==-- Skipping storing options as database already prepared --== PKI CONFIGURATION ==-- PKI is already configured --== APACHE CONFIGURATION ==-- --== SYSTEM CONFIGURATION ==-- --== END OF CONFIGURATION ==-- [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ INFO ] Cleaning stale zombie tasks --== CONFIGURATION PREVIEW ==-- Database name : engine Database secured connection : False Database host : localhost Database user name : engine Database host name validation : False Datbase port : 5432 NFS setup : True Firewall manager : iptables Update Firewall : True Configure WebSocket Proxy : True Host FQDN : tekkaman.localdomain.local NFS mount point : /ISO Set application as default page : True Configure Apache SSL : False Upgrade packages : True Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Cleaning async tasks and compensations [ INFO ] Checking the DB consistency [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Fixing DB inconsistencies [ INFO ] Stage: Package installation [ INFO ] Yum Status: Downloading Packages [ INFO ] Yum Download/Verify: ovirt-engine-3.3.3-1.fc19.noarch [ INFO ] Yum Downloading: (2/8): ovirt-engine-backend-3.3.3-1.fc19.noarch.rpm 1.6 M(44%) [ INFO ] Yum Downloading: (2/8): ovirt-engine-backend-3.3.3-1.fc19.noarch.rpm 2.8 M(76%) [ INFO ] Yum Download/Verify: ovirt-engine-backend-3.3.3-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-dbscripts-3.3.3-1.fc19.noarch [ INFO ] Yum Downloading: (4/8): ovirt-engine-restapi-3.3.3-1.fc19.noarch.rpm 952 k(88%) [ INFO ] Yum Download/Verify: ovirt-engine-restapi-3.3.3-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-tools-3.3.3-1.fc19.noarch [ INFO ] Yum Downloading: (6/8): ovirt-engine-userportal-3.3.3-1.fc19.noarch.rpm 1.0 M(1%) ... [ INFO ] Yum Downloading: (6/8): ovirt-engine-userportal-3.3.3-1.fc19.noarch.rpm 55 M(98%) [ INFO ] Yum Download/Verify: ovirt-engine-userportal-3.3.3-1.fc19.noarch [ INFO ] Yum Downloading: (7/8): ovirt-engine-webadmin-portal-3.3.3-1.fc19.noarch.rpm 1.5 M(1%) ... [ INFO ] Yum Downloading: (7/8): ovirt-engine-webadmin-portal-3.3.3-1.fc19.noarch.rpm 94 M(99%) [ INFO ] Yum Download/Verify: ovirt-engine-webadmin-portal-3.3.3-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-websocket-proxy-3.3.3-1.fc19.noarch [ INFO ] Yum Status: Check Package Signatures [ INFO ] Yum Status: Running Test Transaction [ INFO ] Yum Status: Running Transaction [ INFO ] Yum update: 1/16: ovirt-engine-websocket-proxy-3.3.3-1.fc19.noarch [ INFO ] Yum update: 2/16: ovirt-engine-dbscripts-3.3.3-1.fc19.noarch [ INFO ] Yum update: 3/16: ovirt-engine-restapi-3.3.3-1.fc19.noarch [ INFO ] Yum update: 4/16: ovirt-engine-webadmin-portal-3.3.3-1.fc19.noarch [ INFO ] Yum update: 5/16: ovirt-engine-tools-3.3.3-1.fc19.noarch [ INFO ] Yum update: 6/16: ovirt-engine-userportal-3.3.3-1.fc19.noarch [ INFO ] Yum update: 7/16: ovirt-engine-backend-3.3.3-1.fc19.noarch [ INFO ] Yum update: 8/16: ovirt-engine-3.3.3-1.fc19.noarch [ INFO ] Yum updated: 9/16: ovirt-engine-backend [ INFO ] Yum updated: 10/16: ovirt-engine-dbscripts [ INFO ] Yum updated: 11/16: ovirt-engine-restapi [ INFO ] Yum updated: 12/16: ovirt-engine-tools [ INFO ] Yum updated: 13/16: ovirt-engine-userportal [ INFO ] Yum updated: 14/16: ovirt-engine-webadmin-portal [ INFO ] Yum updated: 15/16: ovirt-engine [ INFO ] Yum updated: 16/16: ovirt-engine-websocket-proxy [ INFO ] Yum Verify: 1/16: ovirt-engine.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 2/16: ovirt-engine-dbscripts.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 3/16: ovirt-engine-restapi.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 4/16: ovirt-engine-webadmin-portal.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 5/16: ovirt-engine-tools.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 6/16: ovirt-engine-userportal.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 7/16: ovirt-engine-websocket-proxy.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 8/16: ovirt-engine-backend.noarch 0:3.3.3-1.fc19 - u [ INFO ] Yum Verify: 9/16: ovirt-engine-websocket-proxy.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 10/16: ovirt-engine-userportal.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 11/16: ovirt-engine-backend.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 12/16: ovirt-engine.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 13/16: ovirt-engine-tools.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 14/16: ovirt-engine-dbscripts.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 15/16: ovirt-engine-webadmin-portal.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Yum Verify: 16/16: ovirt-engine-restapi.noarch 0:3.3.2-1.fc19 - ud [ INFO ] Stage: Misc configuration [ INFO ] Backing up database to '/var/lib/ovirt-engine/backups/engine-20140129223909.I3iTp5.sql'. [ INFO ] Updating database schema [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/var/lib/ovirt-engine/deployments/ovirt-engine-reports.war' [ INFO ] Yum Performing yum transaction rollback [ INFO ] Yum Downloading: fedora/19/x86_64/other_db 4.2 M(51%) [ INFO ] Yum Downloading: google-chrome/filelists (0%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 2.1 M(13%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 5.0 M(32%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 7.4 M(47%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 9.8 M(63%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 12 M(76%) [ INFO ] Yum Downloading: updates/19/x86_64/filelists_db 14 M(91%) [ INFO ] Yum Downloading: updates/19/x86_64/other_db 1.3 M(22%) [ INFO ] Yum Downloading: updates/19/x86_64/other_db 3.5 M(59%) [ INFO ] Yum Status: Downloading Packages [ INFO ] Yum Download/Verify: ovirt-engine-3.3.2-1.fc19.noarch [ INFO ] Yum Downloading: (2/8): ovirt-engine-backend-3.3.2-1.fc19.noarch.rpm 2.7 M(73%) [ INFO ] Yum Download/Verify: ovirt-engine-backend-3.3.2-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-dbscripts-3.3.2-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-restapi-3.3.2-1.fc19.noarch [ INFO ] Yum Download/Verify: ovirt-engine-tools-3.3.2-1.fc19.noarch Is the patch to be put yet for final 3.3.3? Or will there be any particular note in release (for example to deinstall reports..)? Gianluca
On Wed, Jan 29, 2014 at 10:49 PM, Gianluca Cecchi wrote:
[ INFO ] Backing up database to '/var/lib/ovirt-engine/backups/engine-20140129223909.I3iTp5.sql'. [ INFO ] Updating database schema [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/var/lib/ovirt-engine/deployments/ovirt-engine-reports.war' [ INFO ] Yum Performing yum transaction rollback
Is the patch to be put yet for final 3.3.3? Or will there be any particular note in release (for example to deinstall reports..)?
Gianluca
Note that my current situation is: [root@tekkaman ~]# ll /var/lib/ovirt-engine/deployments total 8 lrwxrwxrwx. 1 root root 34 Jan 7 2013 engine.ear -> /usr/share/ovirt-engine/engine.ear -rw-r--r--. 1 ovirt ovirt 10 Dec 21 12:28 engine.ear.deployed lrwxrwxrwx. 1 root root 48 Feb 19 2013 ovirt-engine-reports.war -> /usr/share/ovirt-engine/ovirt-engine-reports.war -rw-r--r--. 1 ovirt ovirt 24 Dec 21 15:43 ovirt-engine-reports.war.dodeploy with /usr/share/ovirt-engine/ovirt-engine-reports.war being a broken link [root@tekkaman ~]# ll /usr/share/ovirt-engine total 52 drwxr-xr-x. 2 root root 4096 Jan 29 22:38 bin drwxr-xr-x. 3 root root 4096 Jan 21 11:10 branding drwxr-xr-x. 2 root root 4096 Jan 21 11:10 conf drwxr-xr-x. 3 root root 4096 Jan 29 22:39 dbscripts drwxr-xr-x. 8 ovirt ovirt 4096 Jan 29 22:38 engine.ear drwxr-xr-x. 2 root root 4096 Jan 29 22:38 files drwxr-xr-x. 4 root root 4096 Jan 21 11:10 firewalld drwxr-xr-x. 2 root root 4096 Jan 29 22:38 manual drwxr-xr-x. 4 root root 4096 Jan 21 11:10 modules drwxr-xr-x. 3 root root 4096 Nov 24 20:51 scripts drwxr-xr-x. 5 root root 4096 Jan 21 11:10 services drwxr-xr-x. 6 root root 4096 Jan 21 11:10 setup drwxr-xr-x. 2 root root 4096 Jan 21 11:10 ui-plugins Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Yaniv Dary" <ydary@redhat.com> Cc: "users" <users@ovirt.org> Sent: Wednesday, January 29, 2014 11:49:04 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
Just to note that on my oVirt 3.3.2-1 allinone on fedora 19, after enabling updates-testing I get the same failure using 3.3.3rc
Can it be that the following is dead symlink? if so please remove. /var/lib/ovirt-engine/deployments/ovirt-engine-reports.war
On Wed, Jan 29, 2014 at 10:55 PM, Alon Bar-Lev wrote:
----- Original Message -----
From: "Gianluca Cecchi" To: "Yaniv Dary" Cc: "users" <users@ovirt.org> Sent: Wednesday, January 29, 2014 11:49:04 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
Just to note that on my oVirt 3.3.2-1 allinone on fedora 19, after enabling updates-testing I get the same failure using 3.3.3rc
Can it be that the following is dead symlink? if so please remove.
/var/lib/ovirt-engine/deployments/ovirt-engine-reports.war
I confirm that - rollback (made automatically during the failed engine-setup first run) - rm /var/lib/ovirt-engine/deployments/ovirt-engine-reports.war - engine-setup again now it completes correctly Probably it is worth to put a note in release notes. But I don't know where: http://wiki.ovirt.org/OVirt_3.3.3_release_notes or http://wiki.ovirt.org/OVirt_3.2_to_3.3_upgrade ? Because I previously used (in December I think) the latest link to migrate from f18+3.2 to f19+3.3.2 Gianluca
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Yaniv Dary" <ydary@redhat.com>, "users" <users@ovirt.org> Sent: Thursday, January 30, 2014 12:20:46 AM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
On Wed, Jan 29, 2014 at 10:55 PM, Alon Bar-Lev wrote:
----- Original Message -----
From: "Gianluca Cecchi" To: "Yaniv Dary" Cc: "users" <users@ovirt.org> Sent: Wednesday, January 29, 2014 11:49:04 PM Subject: Re: [Users] engine reports and dwh setup in 3.3.2
Just to note that on my oVirt 3.3.2-1 allinone on fedora 19, after enabling updates-testing I get the same failure using 3.3.3rc
Can it be that the following is dead symlink? if so please remove.
/var/lib/ovirt-engine/deployments/ovirt-engine-reports.war
I confirm that - rollback (made automatically during the failed engine-setup first run) - rm /var/lib/ovirt-engine/deployments/ovirt-engine-reports.war - engine-setup again now it completes correctly
Probably it is worth to put a note in release notes. But I don't know where: http://wiki.ovirt.org/OVirt_3.3.3_release_notes or http://wiki.ovirt.org/OVirt_3.2_to_3.3_upgrade ? Because I previously used (in December I think) the latest link to migrate from f18+3.2 to f19+3.3.2
I guess both... as people can upgrade directly to 3.3.3
participants (5)
-
Alon Bar-Lev -
Gianluca Cecchi -
Itamar Heim -
Sandro Bonazzola -
Yaniv Dary