[
https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998834#comment-15998834
]
Sangeeta Ravindran commented on AMBARI-20925:
---------------------------------------------
Failure seems unrelated to patch.
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.4:yarn (yarn install) on project
ambari-web: Failed to run task: 'yarn install --ignore-engines --pure-lockfile'
failed. org.apache.commons.exec.ExecuteException: Process exited with an error:
1 (Exit value: 1) -> [Help 1]
> Service Auto-Start behavior is incorrect for Service Administrator and
> Service Operator Roles
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-20925
> URL: https://issues.apache.org/jira/browse/AMBARI-20925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: trunk, 2.5.0
> Reporter: Sangeeta Ravindran
> Assignee: Sangeeta Ravindran
> Fix For: trunk
>
> Attachments: AMBARI-20925_2.5.1.patch, AMBARI-20925_trunk.patch
>
>
> As per the Role based access control list, users with Service Administrator
> role should be able to manage service auto-start while users with Service
> Operator role should not have this privilege.
> Currently, Service Administrators and Service Operators can view Service Auto
> Start menu item, but clicking on it displays the main dashboard.
> Service Operators should not see this menu and Service Administrators should
> be able to navigate to the Service Auto Start page and enable or disable
> auto-start at service level.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
