Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 772001 - Reporting: ETL process is running under root. should run under rhevm
Reporting: ETL process is running under root. should run under rhevm
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh (Show other bugs)
3.0.1
Unspecified Unspecified
medium Severity high
: ---
: 3.3.0
Assigned To: Sandro Bonazzola
Barak Dagan
integration
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-05 10:58 EST by Yaniv Kaul
Modified: 2015-09-22 09 EDT (History)
12 users (show)

See Also:
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 09:58:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
dyasny: Triaged+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 17311 None None None Never
Red Hat Product Errata RHBA-2014:0036 normal SHIPPED_LIVE rhevm-dwh 3.3 bug fix and enhancement update 2014-01-21 14:53:35 EST

  None (edit)
Description Yaniv Kaul 2012-01-05 10:58:37 EST
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:
Comment 1 Barak 2012-06-17 05:56:51 EDT
Alex, was it already handled ?
Comment 2 Alex Lourie 2012-06-18 04:17:57 EDT
Not yet. We will handle it.
Comment 4 Yaniv Lavi 2013-10-03 09:50:25 EDT
Patch wasn't working. Can you fix it?



Yaniv
Comment 5 Alex Lourie 2013-10-03 12:54:17 EDT
It's not trivial. I'm not certain that it is worth fixing prior to moving to otopi-based implementation.
Comment 8 David Botzer 2013-10-17 09:07:45 EDT
IS18.1 has dwh version rhevm-dwh.noarch 0:3.3.0-14.el6ev
Alex, when 3.3.0-15 will be released ?
Comment 9 Barak Dagan 2013-10-23 08:36:07 EDT
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
Comment 10 Charlie 2013-11-27 19:54:33 EST
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.
Comment 13 errata-xmlrpc 2014-01-21 09:58:15 EST
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

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