Bug 1086003

(In reply to Barak Dagan from comment #0)
> Created attachment 884646 [details]
> setup log
> 
> Description of problem:
> During updagrade from clean 3.3.2 to av6.1, the setup fails:
> 
> [ INFO  ] Creating/refreshing DWH database schema
> [ INFO  ] Regenerating Jasper's build configuration files
> [ INFO  ] Exporting data out of Jasper
> [ INFO  ] Backing up database *:rhevmreports to
> '/var/lib/ovirt-engine-reports/backups/reports-20140410020529.dMFuN6.sql'.
> [ INFO  ] Deploying Jasper
> [ ERROR ] Failed to execute stage 'Misc configuration': Command './js-ant'
> failed to execute                                                           
> 

The error is:

execute-output: ('./js-ant', '-DmasterPropsSource=/tmp/tmp9npIPO/config', 'deploy-webapp-pro') stderr:

BUILD FAILED
/usr/share/jasperreports-server-pro/buildomatic/bin/app-server.xml:833: Warning: Could not find file /var/lib/install_resources/jboss7/jboss-deployment-structure.xml to copy.

I also stumbled upon this during verifying http://gerrit.ovirt.org/26005 and http://gerrit.ovirt.org/25998 but did not manage to reproduce. Also consulted Yaniv trying to figure out why it tries to access /var/lib/install_resources and we did not mange to find a reason for this.

Please try to reproduce under strace, hopefully it will give us a clue. Something like:

strace -f -o /tmp/strace-setup.log -tt -s 0 /usr/bin/engine-setup

Thanks!

Logs are too large to upload, sending them offline

(Following lots of tests by Barak, some more searches etc., consulting Alon)

Seems like it's just a recent fix to jasper [1]

On a system with jasperreports-server-pro-5.5.0-9.el6ev.noarch, I have the file /usr/share/jasperreports-server-pro/buildomatic/bin/app-server.xml patched to do:

                            <equals arg1="${app-server_AppServer}" arg2="jboss_EAP6orAS7" />
                            <then>
                                <copy file="${basedir}/install_resources/jboss7/jboss-deployment-structure.xml" toDir="${warTargetDir}/META-INF" overwrite="true"/>
                                <copy file="${currentConf}/js-jboss7-ds.xml" toDir="${warTargetDir}/WEB-INF" overwrite="true"/>
                                <touch file="${jbossDeployDir}/${webAppName}.war.dodeploy"/>
                            </then>

But on the test system of Barak, with jasperreports-server-pro-5.5.0-6.el6ev.noarch, it has:

                            <equals arg1="${app-server_AppServer}" arg2="jboss_EAP6orAS7" />
                            <then>
                                <copy file="${currentConf}/../../install_resources/jboss7/jboss-deployment-structure.xml" toDir="${warTargetDir}/META-INF" overwrite="true"/>
                                <copy file="${currentConf}/js-jboss7-ds.xml" toDir="${warTargetDir}/WEB-INF" overwrite="true"/>
                                <touch file="${jbossDeployDir}/${webAppName}.war.dodeploy"/>
                            </then>

[1] http://gerrit.ovirt.org/23303

Barak - please try again from scratch with an updated jasper reports package.

If it works for you, we should probably change the Require line to use a recent version. We currently require >= 5.5.0-6 .

Yaniv if this is the case -  who should change the require >= 5.5.0-6 dependency

(In reply to Barak from comment #4)
> Yaniv if this is the case -  who should change the require >= 5.5.0-6
> dependency

I do, Yaniv can too - it's a trivial fix. Is it?

upgrading jasperreports-server-pro from 5.5.0-6.el6ev to 5.5.0-9.el6ev beforehand does solve the issue.

Please update the dependency.

Verified on av8.1 upgraded from is35:

[ INFO  ] Yum Status: Downloading Packages
[ INFO  ] Yum Download/Verify: jasperreports-server-pro-5.5.0-9.el6ev.noarch
[ INFO  ] Yum Download/Verify: patch-2.6-6.el6.x86_64
[ INFO  ] Yum Download/Verify: rhevm-dwh-3.4.0-8.el6ev.noarch
[ INFO  ] Yum Download/Verify: rhevm-reports-3.4.0-7.el6ev.noarch
[ INFO  ] Yum Status: Check Package Signatures
[ INFO  ] Yum Status: Running Test Transaction
[ INFO  ] Yum Status: Running Transaction
[ INFO  ] Yum update: 1/7: jasperreports-server-pro-5.5.0-9.el6ev.noarch
[ INFO  ] Yum install: 2/7: patch-2.6-6.el6.x86_64
[ INFO  ] Yum update: 3/7: rhevm-reports-3.4.0-7.el6ev.noarch
[ INFO  ] Yum update: 4/7: rhevm-dwh-3.4.0-8.el6ev.noarch
[ INFO  ] Yum updated: 5/7: rhevm-reports
[ INFO  ] Yum updated: 6/7: jasperreports-server-pro
[ INFO  ] Yum updated: 7/7: rhevm-dwh
[ INFO  ] Yum Verify: 1/7: rhevm-dwh.noarch 0:3.4.0-8.el6ev - u
[ INFO  ] Yum Verify: 2/7: patch.x86_64 0:2.6-6.el6 - u
[ INFO  ] Yum Verify: 3/7: rhevm-reports.noarch 0:3.4.0-7.el6ev - u
[ INFO  ] Yum Verify: 4/7: jasperreports-server-pro.noarch 0:5.5.0-9.el6ev - u
[ INFO  ] Yum Verify: 5/7: rhevm-dwh.noarch 0:3.3.2-1.el6ev - ud
[ INFO  ] Yum Verify: 6/7: rhevm-reports.noarch 0:3.3.2-3.el6ev - ud
[ INFO  ] Yum Verify: 7/7: jasperreports-server-pro.noarch 0:5.5.0-6.el6ev - ud

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0602.html

Created attachment 928980 [details]
engine-setup log

The log for the bug

Hi, 

You didn't attach the correct logs.

Shirly

The log is located at /var/log/ovirt-engine/setup/

Shirly

Created attachment 929079 [details]
ovirt-setup log

(In reply to liuwei from comment #17)
> Created attachment 929079 [details]
> ovirt-setup log

I had uploaded it

This happened because the host name wasn't fully resolvable like required.
Please correct this.



Yaniv

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days