Bug 1155035 - There is a problem on execve() during setup ovirt-engine-reports
Summary: There is a problem on execve() during setup ovirt-engine-reports
Keywords:
Status: CLOSED DUPLICATE of bug 1155028
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-reports
Version: 3.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Shirly Radco
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-21 09:52 UTC by zhangyaqi
Modified: 2014-11-12 06:34 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-23 12:48:05 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description zhangyaqi 2014-10-21 09:52:48 UTC
Description of problem:
i plan to test Separate Reports Host. And when I setup ovirt-engine-reports, I have encountered some problems like following:

Configuring PostgreSQL
[ INFO  ] Deploying Jasper
[ ERROR ] Failed to execute stage 'Misc configuration': execve() arg 3 contains a non-string value
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Rolling back Reports database schema
[ INFO  ] Clearing Reports database ovirt_engine_reports
[ INFO  ] Rolling back Reports files
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20141021232448-snc1qo.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20141021234050-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. vmA:yum install ovirt-engine;
2. vmB:yum install ovirt-engine-dwh;
3. vmC:yum install ovirt-engine-reports;
4. vmA:engine-setup;   successful
5. vmB:engine-setup;   successful
6. vmC:engine-setup;   failed , and u will see that issue.

Actual results:
[ ERROR ] Execution of setup failed

Expected results:
Execution of setup completed successfully

Additional info:

Comment 1 Shirly Radco 2014-10-21 10:50:29 UTC
Please attach the logs from the reports vm.
Please describe the environment, os, rpms installed for engine, dwh and reports.

Comment 2 Shirly Radco 2014-10-23 12:48:05 UTC

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

Comment 3 zhangyaqi 2014-11-12 02:53:41 UTC
(In reply to Shirly Radco from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 1155028 ***

hi all, 
  
       i am so sorry about my procrastination. And since i update the dwh and reports to 3.5.1-0.0.master.20141030081440, i have found that this issue is already gone. So, if your fix it, or something else , i have no idea about that. Have the upstream update it ? Thank u.

Comment 4 Shirly Radco 2014-11-12 06:06:11 UTC
(In reply to zhangyaqi from comment #3)
> (In reply to Shirly Radco from comment #2)
> > 
> > *** This bug has been marked as a duplicate of bug 1155028 ***
> 
> hi all, 
>   
>        i am so sorry about my procrastination. And since i update the dwh
> and reports to 3.5.1-0.0.master.20141030081440, i have found that this issue
> is already gone. So, if your fix it, or something else , i have no idea
> about that. Have the upstream update it ? Thank u.

This is fixed in the snapshots and will be available next release.

Shirly

Comment 5 zhangyaqi 2014-11-12 06:34:33 UTC
(In reply to Shirly Radco from comment #4)
> (In reply to zhangyaqi from comment #3)
> > (In reply to Shirly Radco from comment #2)
> > > 
> > > *** This bug has been marked as a duplicate of bug 1155028 ***
> > 
> > hi all, 
> >   
> >        i am so sorry about my procrastination. And since i update the dwh
> > and reports to 3.5.1-0.0.master.20141030081440, i have found that this issue
> > is already gone. So, if your fix it, or something else , i have no idea
> > about that. Have the upstream update it ? Thank u.
> 
> This is fixed in the snapshots and will be available next release.
> 
> Shirly

merci  ^.^


Note You need to log in before you can comment on or make changes to this bug.