[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713314#comment-15713314 ] Hudson commented on AMBARI-19052: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6131 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6131/]) AMBARI-19052. Re-arrange "Role Based Access Control" info table (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=63c0f2e58fc09b709e890923752c4ccb04181180]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/RoleDetailsModal.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/modals/RoleDetailsModal.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712972#comment-15712972 ] Hudson commented on AMBARI-19052: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #433 (See [https://builds.apache.org/job/Ambari-branch-2.5/433/]) AMBARI-19052. Re-arrange "Role Based Access Control" info table (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ab3d72914254b9ee13708cb8a5987d0a2c4459a9]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/modals/RoleDetailsModal.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/RoleDetailsModal.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[
https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712689#comment-15712689
]
Hadoop QA commented on AMBARI-19052:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841318/AMBARI-19052.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9487//console
This message is automatically generated.
> Re-arrange "Role Based Access Control" info table
> -
>
> Key: AMBARI-19052
> URL: https://issues.apache.org/jira/browse/AMBARI-19052
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19052.patch
>
>
> The RBAC info table should be organized so that the permissions flow down
> like below:
> ||Permissions||Role 1||Role 2||Role 3||
> |Perm 1|(/)|(/)|(/)|
> |Perm 2| |(/)|(/)|
> |Perm 3| | |(/)|
> We have areas in the table where it doesn't look like that, for example "View
> service operational logs" should be right after "Manage configuration groups".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[ https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712672#comment-15712672 ] Aleksandr Kovalenko commented on AMBARI-19052: -- Patch consist of changes for ambari-admin, checking these unit tests are not included to Hadoop QA job. > Re-arrange "Role Based Access Control" info table > - > > Key: AMBARI-19052 > URL: https://issues.apache.org/jira/browse/AMBARI-19052 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19052.patch > > > The RBAC info table should be organized so that the permissions flow down > like below: > ||Permissions||Role 1||Role 2||Role 3|| > |Perm 1|(/)|(/)|(/)| > |Perm 2| |(/)|(/)| > |Perm 3| | |(/)| > We have areas in the table where it doesn't look like that, for example "View > service operational logs" should be right after "Manage configuration groups". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19052) Re-arrange "Role Based Access Control" info table
[
https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712577#comment-15712577
]
Hadoop QA commented on AMBARI-19052:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841318/AMBARI-19052.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9486//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9486//console
This message is automatically generated.
> Re-arrange "Role Based Access Control" info table
> -
>
> Key: AMBARI-19052
> URL: https://issues.apache.org/jira/browse/AMBARI-19052
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19052.patch
>
>
> The RBAC info table should be organized so that the permissions flow down
> like below:
> ||Permissions||Role 1||Role 2||Role 3||
> |Perm 1|(/)|(/)|(/)|
> |Perm 2| |(/)|(/)|
> |Perm 3| | |(/)|
> We have areas in the table where it doesn't look like that, for example "View
> service operational logs" should be right after "Manage configuration groups".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
