[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk

[jira] [Commented] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully

[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528468#comment-15528468 ] Hadoop QA commented on AMBARI-18355: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18477) Alert unit tests failing on trunk

[ https://issues.apache.org/jira/browse/AMBARI-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18477: - Status: Patch Available (was: Open) > Alert unit tests failing on trunk >

[jira] [Updated] (AMBARI-18477) Alert unit tests failing on trunk

[ https://issues.apache.org/jira/browse/AMBARI-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18477: - Attachment: AMBARI-18477.patch > Alert unit tests failing on trunk >

[jira] [Created] (AMBARI-18477) Alert unit tests failing on trunk

Andrew Onischuk created AMBARI-18477: Summary: Alert unit tests failing on trunk Key: AMBARI-18477 URL: https://issues.apache.org/jira/browse/AMBARI-18477 Project: Ambari Issue Type: Bug

[jira] [Commented] (AMBARI-18401) Allow running a subset of Python unit tests

[ https://issues.apache.org/jira/browse/AMBARI-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528212#comment-15528212 ] Hadoop QA commented on AMBARI-18401: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor

[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528125#comment-15528125 ] Hadoop QA commented on AMBARI-17898: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-12415) Ambari should set dr. who in the admin acl by default in the secure cluster

[ https://issues.apache.org/jira/browse/AMBARI-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528045#comment-15528045 ] Yuanbo Liu commented on AMBARI-12415: - Yes I agree with Jeffrey, adding "dr.who" into admin acl is

[jira] [Commented] (AMBARI-18441) upgrade ambari to 2.1.1 error

[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527978#comment-15527978 ] Hadoop QA commented on AMBARI-18441: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-17945) Ranger UserSync restart failed during EU from 2.2.9 to 2.4.2

[ https://issues.apache.org/jira/browse/AMBARI-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17945: - Fix Version/s: 2.4.0 > Ranger UserSync restart failed during EU from 2.2.9 to

[jira] [Commented] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client

[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527665#comment-15527665 ] Hadoop QA commented on AMBARI-18423: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18313) Capacity Scheduler View: Xml diff view tool to show changes made and queue capacity chart

[ https://issues.apache.org/jira/browse/AMBARI-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527403#comment-15527403 ] Hadoop QA commented on AMBARI-18313: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18467) Ambari server does not come up after restart if cluster install fails.

[ https://issues.apache.org/jira/browse/AMBARI-18467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527360#comment-15527360 ] Hadoop QA commented on AMBARI-18467: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18470) RU/EU cannot start because ServiceCheckValidityCheck incorrectly calculates Service Checks that ran

[ https://issues.apache.org/jira/browse/AMBARI-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527356#comment-15527356 ] Hadoop QA commented on AMBARI-18470: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527338#comment-15527338 ] Hudson commented on AMBARI-18474: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #86 (See

[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication

[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Summary: Ambari UI changes to support PAM authentication (was: Ambari UI changes

[jira] [Created] (AMBARI-18476) Ambari UI changes to suppor PAM authentication

Sangeeta Ravindran created AMBARI-18476: --- Summary: Ambari UI changes to suppor PAM authentication Key: AMBARI-18476 URL: https://issues.apache.org/jira/browse/AMBARI-18476 Project: Ambari

[jira] [Commented] (AMBARI-18463) Regression: krb5JAASLogin.conf is not updated during secure BP install

[ https://issues.apache.org/jira/browse/AMBARI-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15527115#comment-15527115 ] Hadoop QA commented on AMBARI-18463: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18474: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to

[jira] [Commented] (AMBARI-18459) Print error messages if bulkcommand section of a component includes non-existing component

[ https://issues.apache.org/jira/browse/AMBARI-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526886#comment-15526886 ] Di Li commented on AMBARI-18459: unit test errors occurred since at least the AMBARI-18464. Provide

[jira] [Updated] (AMBARI-18467) Ambari server does not come up after restart if cluster install fails.

[ https://issues.apache.org/jira/browse/AMBARI-18467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18467: - Attachment: ambari-server.log.gz > Ambari server does not come up after restart if

[jira] [Commented] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526837#comment-15526837 ] Hadoop QA commented on AMBARI-18471: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (AMBARI-18459) Print error messages if bulkcommand section of a component includes non-existing component

[ https://issues.apache.org/jira/browse/AMBARI-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526814#comment-15526814 ] Hudson commented on AMBARI-18459: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5730 (See

[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526815#comment-15526815 ] Hudson commented on AMBARI-18051: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5730 (See

[jira] [Commented] (AMBARI-18472) Can't switch to not current version for not default config gorup

[ https://issues.apache.org/jira/browse/AMBARI-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526744#comment-15526744 ] Hadoop QA commented on AMBARI-18472: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18051: Status: Open (was: Patch Available) > Services should be able to provide their own pre-req

[jira] [Assigned] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades

[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-10642: -- Assignee: Juanjo Marron > Mechanism to automatically update Ambari versions in

[jira] [Comment Edited] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades

[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526702#comment-15526702 ] Juanjo Marron edited comment on AMBARI-10642 at 9/27/16 4:47 PM: - Solve

[jira] [Resolved] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades

[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-10642. Resolution: Duplicate Fix Version/s: 2.4.0 > Mechanism to automatically update

[jira] [Commented] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades

[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526702#comment-15526702 ] Juanjo Marron commented on AMBARI-10642: Solve in AMBARI-15636: Use a new concept called a

[jira] [Updated] (AMBARI-18473) Scope and Services need to be used for orchestration

[ https://issues.apache.org/jira/browse/AMBARI-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-18473: --- Attachment: AMBARI-18473.patch > Scope and Services need to be used for orchestration >

[jira] [Updated] (AMBARI-18473) Scope and Services need to be used for orchestration

[ https://issues.apache.org/jira/browse/AMBARI-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-18473: --- Status: Patch Available (was: In Progress) > Scope and Services need to be used for orchestration

[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526664#comment-15526664 ] Hadoop QA commented on AMBARI-18051: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526661#comment-15526661 ] Hadoop QA commented on AMBARI-18474: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18050) Upgrade pre-req check code needs to be decoupled from CheckDescription class

[ https://issues.apache.org/jira/browse/AMBARI-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526632#comment-15526632 ] Hudson commented on AMBARI-18050: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #85 (See

[jira] [Created] (AMBARI-18475) Remove Global Cluster Lock Shared Between Business Objects

Jonathan Hurley created AMBARI-18475: Summary: Remove Global Cluster Lock Shared Between Business Objects Key: AMBARI-18475 URL: https://issues.apache.org/jira/browse/AMBARI-18475 Project: Ambari

[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18474: - Status: Patch Available (was: Open) > Kerberos wizard loses request id on

[jira] [Commented] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526489#comment-15526489 ] Aleksandr Kovalenko commented on AMBARI-18474: -- +1 for the patch > Kerberos wizard loses

[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18474: - Attachment: AMBARI-18474.patch > Kerberos wizard loses request id on server

[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on server restart

[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18474: - Attachment: Screen Shot 2016-09-20 at 6.37.29 PM.png > Kerberos wizard loses

[jira] [Created] (AMBARI-18474) Kerberos wizard loses request id on server restart

Antonenko Alexander created AMBARI-18474: Summary: Kerberos wizard loses request id on server restart Key: AMBARI-18474 URL: https://issues.apache.org/jira/browse/AMBARI-18474 Project: Ambari

[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526459#comment-15526459 ] Tim Thorpe commented on AMBARI-18051: - Thanks [~rlevas]. Pushed the change with the license header.

[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526403#comment-15526403 ] Robert Levas commented on AMBARI-18051: --- [~Tim Thorpe],

[jira] [Updated] (AMBARI-18459) Print error messages if bulkcommand section of a component includes non-existing component

[ https://issues.apache.org/jira/browse/AMBARI-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18459: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Print error messages if bulkcommand

[jira] [Commented] (AMBARI-18459) Print error messages if bulkcommand section of a component includes non-existing component

[ https://issues.apache.org/jira/browse/AMBARI-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526392#comment-15526392 ] Di Li commented on AMBARI-18459: pushed to trunk as

[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

[ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526377#comment-15526377 ] Hudson commented on AMBARI-18051: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5729 (See

[jira] [Updated] (AMBARI-18469) Fix custom jdbc functionality for ambari-server setup

[ https://issues.apache.org/jira/browse/AMBARI-18469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18469: --- Attachment: AMBARI-18469.patch > Fix custom jdbc functionality for ambari-server

[jira] [Updated] (AMBARI-18469) Fix custom jdbc functionality for ambari-server setup

[ https://issues.apache.org/jira/browse/AMBARI-18469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18469: --- Attachment: (was: AMBARI-18469.patch) > Fix custom jdbc functionality for

[jira] [Created] (AMBARI-18473) Scope and Services need to be used for orchestration

Nate Cole created AMBARI-18473: -- Summary: Scope and Services need to be used for orchestration Key: AMBARI-18473 URL: https://issues.apache.org/jira/browse/AMBARI-18473 Project: Ambari Issue

[jira] [Commented] (AMBARI-18466) Component should be renamed to "Microsoft R Server Client"

[ https://issues.apache.org/jira/browse/AMBARI-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525806#comment-15525806 ] Hudson commented on AMBARI-18466: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #84 (See

[jira] [Commented] (AMBARI-18472) Can't switch to not current version for not default config gorup

[ https://issues.apache.org/jira/browse/AMBARI-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525766#comment-15525766 ] Aleksandr Kovalenko commented on AMBARI-18472: -- +1 for the patch > Can't switch to not

[jira] [Updated] (AMBARI-18472) Can't switch to not current version for not default config gorup

[ https://issues.apache.org/jira/browse/AMBARI-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18472: -- Status: Patch Available (was: Open) 30364 tests complete (24 seconds) 151 tests

[jira] [Updated] (AMBARI-18472) Can't switch to not current version for not default config gorup

[ https://issues.apache.org/jira/browse/AMBARI-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18472: -- Attachment: AMBARI-18472.patch > Can't switch to not current version for not default

[jira] [Created] (AMBARI-18472) Can't switch to not current version for not default config gorup

Andrii Babiichuk created AMBARI-18472: - Summary: Can't switch to not current version for not default config gorup Key: AMBARI-18472 URL: https://issues.apache.org/jira/browse/AMBARI-18472

[jira] [Commented] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525751#comment-15525751 ] Hadoop QA commented on AMBARI-18471: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (AMBARI-14526) CentOS 7.2/RHEL 7.2 ambari-server systemd script is broken

[ https://issues.apache.org/jira/browse/AMBARI-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Kropp updated AMBARI-14526: --- Attachment: AMBARI-14526.patch > CentOS 7.2/RHEL 7.2 ambari-server systemd script is broken

[jira] [Commented] (AMBARI-14526) CentOS 7.2/RHEL 7.2 ambari-server systemd script is broken

[ https://issues.apache.org/jira/browse/AMBARI-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525699#comment-15525699 ] Henning Kropp commented on AMBARI-14526: Seems that AMBARI-15090 breaks this for RHEL 7.2. With

[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Attachment: AMBARI-18471.patch > Refactor yarn() function in YARN service. Part 1. >

[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Attachment: (was: AMBARI-18471.patch) > Refactor yarn() function in YARN service.

[jira] [Commented] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525616#comment-15525616 ] Hadoop QA commented on AMBARI-18471: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18466) Component should be renamed to "Microsoft R Server Client"

[ https://issues.apache.org/jira/browse/AMBARI-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18466: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to

[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Description: Fix the most obvious points of the main jira: 1\. Refactor this code to

[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Attachment: AMBARI-18471.patch > Refactor yarn() function in YARN service. Part 1. >

[jira] [Created] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

Andrew Onischuk created AMBARI-18471: Summary: Refactor yarn() function in YARN service. Part 1. Key: AMBARI-18471 URL: https://issues.apache.org/jira/browse/AMBARI-18471 Project: Ambari

[jira] [Updated] (AMBARI-18471) Refactor yarn() function in YARN service. Part 1.

[ https://issues.apache.org/jira/browse/AMBARI-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18471: - Status: Patch Available (was: Open) > Refactor yarn() function in YARN service. Part

[jira] [Updated] (AMBARI-18466) Component should be renamed to "Microsoft R Server Client"

[ https://issues.apache.org/jira/browse/AMBARI-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-18466: --- Status: Patch Available (was: Open) > Component should be renamed to "Microsoft R