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/11/22 21:48:59 UTC
[jira] [Commented] (AMBARI-18964) unable to add users permission
for tez view
[ https://issues.apache.org/jira/browse/AMBARI-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688003#comment-15688003 ]
Hadoop QA commented on AMBARI-18964:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12840119/AMBARI-18964.branch-2.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9358//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9358//console
This message is automatically generated.
> unable to add users permission for tez view
> -------------------------------------------
>
> Key: AMBARI-18964
> URL: https://issues.apache.org/jira/browse/AMBARI-18964
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-18964.branch-2.4.patch, Screen Shot 2016-11-22 at 13.45.25.png
>
>
> During upgrade from 2.4.0, the privileges for the tez view got migrated to the new tez view version but after a restart the same privileges again got inserted into the privilege table(due to a piece of view migration that runs during every restart) and hence in the admin view while opening the tez view instance, JS errors were thrown which prevented insertion of further users to the permission box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)