Oozie warden.ooziee.conf not placed in correct location while installing Mapr packages

Bug #1607704 reported by Vipul Nayyar
6
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: RemoteCommandException: Error during command execution: "sudo -u mapr maprcli node services -name oozie -action start -nodes 11.11.11.8"
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/oozie/oozie-4.1.0/conf is not copied to the location /opt/mapr/conf/conf.d where other warden process config files are stored.

Revision history for this message
Vitalii Gridnev (vgridnev) wrote :

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.

Changed in sahara:
status: New → Incomplete
Revision history for this message
Vitalii Gridnev (vgridnev) wrote :

With 5.1.0 plugin

Revision history for this message
Vipul Nayyar (vipulnayyar) wrote :

I'll try to test this on the latest master code, but I wanted this bug filed here for posterity as this is not documented.

For the config I used : Centos Mapr 5.0.0 on Openstack Liberty 3.0.2, I edited the sahara pre-built image with guestfish tool and added the warden.ooziee.conf originally present in /opt/mapr/oozie/oozie-4.1.0/conf to /opt/mapr/conf/conf.d directory. Then uploaded the edited image again to glance and booted the cluster after registering it with Mapr plugin again.

Hope this helps someone !!

Revision history for this message
Grigoriy (groghkov) wrote :

It has to be reproducible only on Liberty and earlier versions. The root cause is that MapR plugin creates mapr user after oozie instalation. After Liberty release mapr-oozie-4.2 was released and in 4.2 they changed the instalation process that it requires mapr user to be created before oozie install, they also backported this change into mapr-oozie 4.1, so it broke the configuration. This is not the only issue that comes from backporing changes into old version of mapr-ecosystem. In hive 1.0 they changed property name, so, most likely, hive is broken too.

Revision history for this message
Vitalii Gridnev (vgridnev) wrote :

Thanks Grigory. I think it ok now to Invalidate bug.

Changed in sahara:
status: Incomplete → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to sahara (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/350566

Changed in sahara:
status: Invalid → Confirmed
Changed in sahara:
status: Confirmed → In Progress
milestone: none → newton-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to sahara (master)

Reviewed: https://review.openstack.org/350566
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=3340affd16cb4814e6ea74706ebe68e6d763e1c2
Submitter: Jenkins
Branch: master

commit 3340affd16cb4814e6ea74706ebe68e6d763e1c2
Author: Grigoriy Rozhkov <email address hidden>
Date: Fri Aug 12 16:17:32 2016 +0300

    copying oozie.warden to prevent failure

    copying oozie.warden.conf should prevent possible
    issues with packages installation.

    Related bug: 1607704

    Change-Id: I33e8f19037f61c1cbd310d7d703383083715f658

Changed in sahara:
status: In Progress → Fix Released
Changed in sahara:
assignee: nobody → Grigoriy (groghkov)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.