You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/07/28 13:35:20 UTC

[jira] [Commented] (AMBARI-17945) Ranger UserSync restart failed during EU from 2.2.9 to 2.4.2

    [ https://issues.apache.org/jira/browse/AMBARI-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397531#comment-15397531 ] 

Hadoop QA commented on AMBARI-17945:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12820698/AMBARI-17945.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8202//console

This message is automatically generated.

> Ranger UserSync restart failed during EU from 2.2.9 to 2.4.2
> ------------------------------------------------------------
>
>                 Key: AMBARI-17945
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17945
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Blocker
>         Attachments: AMBARI-17945.patch
>
>
> As part of changes done in this AMBARI-17840, following changes are required to handle EU scenario :
> 1] need to change the owner/mode of stop script and 
> 2] create symbolic link if it does not exists.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)