Bug 772001
| Summary: | Reporting: ETL process is running under root. should run under rhevm | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yaniv Kaul <ykaul> |
| Component: | ovirt-engine-dwh | Assignee: | Sandro Bonazzola <sbonazzo> |
| Status: | CLOSED ERRATA | QA Contact: | Barak Dagan <bdagan> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0.1 | CC: | acathrow, bazulay, ecohen, iheim, jkt, mkenneth, oschreib, pstehlik, Rhev-m-bugs, srevivo, yeylon, ylavi |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | 3.3.0 | Flags: | dyasny:
Triaged+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | rhevm-dwh-3.3.0-15.el6ev.noarch.rpm | Doc Type: | Bug Fix |
| Doc Text: |
The rhevm-dwh service was previously running with the 'root' user. It is now run with the 'ovirt' user, which is the same as the engine service.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-21 14:58:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Alex, was it already handled ? Not yet. We will handle it. Patch wasn't working. Can you fix it? Yaniv It's not trivial. I'm not certain that it is worth fixing prior to moving to otopi-based implementation. Merged into master; http://gerrit.ovirt.org/gitweb?p=ovirt-dwh.git;a=commit;h=07fc963a35f4e0391e745ec6b0b616b7854b0e8a IS18.1 has dwh version rhevm-dwh.noarch 0:3.3.0-14.el6ev Alex, when 3.3.0-15 will be released ? verified on IS19 jasperreports-server-pro-5.5.0-3.el6ev.noarch rhevm-reports-3.3.0-12.el6ev.noarch rhevm-dwh-3.3.0-15.el6ev.noarch ETL process (ovirt-engine-dwhd service) runs with the same user as the engine: ovirt 12527 1 3 15:32 ? 00:00:01 /usr/lib/jvm/jre/bin/java -Xms256M -Xmx1024M -cp /usr/share/ovirt-engine-dwh/etl:/usr/share/java/ovirt-engine-dwh/historyETLProcedure.jar:/usr/share/java/ovirt-engine-dwh/advancedPersistentLookupLib.jar:/usr/share/java/ovirt-engine-dwh/talendRoutines.jar:/usr/share/java/dom4j.jar:/usr/share/java/commons-collections.jar:/usr/share/java/log4j.jar:/usr/share/java/postgresql-jdbc.jar ovirt_engine_dwh.historyetl_3_3.HistoryETL --context=Default ovirt 25532 1 0 Oct22 ? 00:00:09 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --pidfile=/var/run/ovirt-websocket-proxy.pid --background --redirect-output start This bug is currently attached to errata RHEA-2013:15116. 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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 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. http://rhn.redhat.com/errata/RHBA-2014-0036.html |
Description of problem: /etc/init.d/ : # if RHEVM_USER is not set, use root if [ -z "$RHEVM_USER" ]; then RHEVM_USER="root" As opposed to rhevm-notifierd, which just simply has: RHEVM_USER="rhevm" which makes everything so much simpler... Is there a valid reason why it's not running as 'rhevm' ? Version-Release number of selected component (if applicable): 3.0.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: