Red Hat Bugzilla – Bug 1026091
Setup - Failure on missing file.
Last modified: 2014-01-21 09:56:18 EST
Description of problem:
engine.conf is not present in latest build and reports setup fails on this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install engine IS21
2. install reports+dwh
fails on missing config file
should not fail.
*** Bug 1027116 has been marked as a duplicate of this bug. ***
Verified in IS23, rhevm-reports-3.3.0-20.el6ev.noarch:
ls: cannot access /etc/ovirt-engine/engine.conf: No such file or directory
# rhevm-reports-setup -a 33.local.reports.answerfile
Welcome to ovirt-engine-reports setup utility
Editing XML files... [ DONE ]
Setting DB connectivity... [ DONE ]
Deploying Server... [ 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.
The installation log file is available at: /var/log/ovirt-engine/ovirt-engine-reports-setup-2013_11_18_18_26_40.log
This bug is currently attached to errata RHEA-2013:15115. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.