Oozie warden.ooziee.conf not placed in correct location while installing Mapr packages
Bug #1607704 reported by
Vipul Nayyar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
Undecided
|
Grigoriy |
Bug Description
In the configuration phase of a Mapr 5.0.0 CentOS cluster in Openstack Liberty 3.0.2, warden fails to start oozie with the following error:
Error during operating on cluster (reason: RemoteCommandEx
ERROR (10002) - Service: oozie is not configured on node:
The reason for this is that after oozie rpm packages are installed, the warden.oozie.conf file originally present in /opt/mapr/
Changed in sahara: | |
status: | Invalid → Confirmed |
Changed in sahara: | |
status: | Confirmed → In Progress |
milestone: | none → newton-3 |
Changed in sahara: | |
status: | In Progress → Fix Released |
Changed in sahara: | |
assignee: | nobody → Grigoriy (groghkov) |
To post a comment you must log in.
Is it reproducible on the latest master code? I think that we can't backport that to stable/liberty because it's now open for security fixes and for critical bugs.