[
https://issues.apache.org/jira/browse/AMBARI-24107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514085#comment-16514085
]
Hudson commented on AMBARI-24107:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9463 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9463/])
[AMBARI-24107] Ranger & Atlas initial install require additional
(ishanbhatt.1989:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=264347cdaf5a23ecb32a30f16f5fda25f9152fb5])
* (edit) ambari-web/test/controllers/wizard/step4_test.js
* (edit) ambari-web/app/controllers/wizard/step4_controller.js
* (edit) ambari-web/app/controllers/wizard/step7_controller.js
* (edit) ambari-web/app/messages.js
> Ranger & Atlas initial install require additional properties to be explicitly
> configured in the UI
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24107
> URL: https://issues.apache.org/jira/browse/AMBARI-24107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Reporter: Ishan Bhatt
> Assignee: Ishan Bhatt
> Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Great to see Ambari now allows deployment of Ranger and Altas services at
> initial cluster install time. However, doing so complicates the install
> process, as there are some additional configurations the user is required to
> explicitly fill. Could we pre-populate this information, as to avoid
> interrupting the install flow?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
