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

Hudson commented on AMBARI-23404:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8950 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8950/])
AMBARI-23404. Customize Services - when user is changed in accounts tab 
(aantonenko: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=8c14b778387b0682982d5e16567e70ad82111664])
* (add) ambari-web/app/mixins/wizard/wizard_misc_property_checker.js
* (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js
* (edit) ambari-web/app/views/wizard/step7/accounts_tab_view.js
* (edit) ambari-web/app/mixins.js


> Customize Services - when user is changed in accounts tab no warning shown to 
> adjust other dependent properties , though shown when navigate to Misc Tab    
>   
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-23404
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23404
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 1) Modify the property Yarn user under Accounts tab. 
> 2) Click Next to Navigate to All Configurations Tab . Chose Misc from Service 
> Selection Dropdown. User will see a pop up to adjust a property 
> yarn.admin.acl which is affected because of user change.
> If user doesn't navigate to Misc tab , he is able to proceed with this effect 
> going unchanged and unnoticed.
> This is not even shown in Review Recommendations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to