[jira] [Commented] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked

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

[jira] [Commented] (AMBARI-22226) RU: Downgrade is failed ZKFC

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

[jira] [Commented] (AMBARI-22225) Cluster created using Blueprints rejects hosts even though their host_name matches host predicate

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

[jira] [Created] (AMBARI-22227) Unit tests for Registry

Madhuvanthi Radhakrishnan created AMBARI-7: -- Summary: Unit tests for Registry Key: AMBARI-7 URL: https://issues.apache.org/jira/browse/AMBARI-7 Project: Ambari Issue

[jira] [Commented] (AMBARI-22224) host and hostname built-in variables are not populated when performing Kerberos-related operations

[ https://issues.apache.org/jira/browse/AMBARI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202638#comment-16202638 ] Hudson commented on AMBARI-4: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #377 (See

[jira] [Updated] (AMBARI-22209) HdpCoreMpack: Quick Links should show NN web UI links

[ https://issues.apache.org/jira/browse/AMBARI-22209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22209: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HdpCoreMpack:

[jira] [Updated] (AMBARI-22209) HdpCoreMpack: Quick Links should show NN web UI links

[ https://issues.apache.org/jira/browse/AMBARI-22209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22209: --- Status: Patch Available (was: Open) Committed to branch-feature-AMBARI-14714 >

[jira] [Updated] (AMBARI-22226) RU: Downgrade is failed ZKFC

[ https://issues.apache.org/jira/browse/AMBARI-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-6: --- Status: Patch Available (was: Open) > RU: Downgrade is failed ZKFC >

[jira] [Updated] (AMBARI-22226) RU: Downgrade is failed ZKFC

[ https://issues.apache.org/jira/browse/AMBARI-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-6: --- Attachment: AMBARI-6.patch > RU: Downgrade is failed ZKFC > > >

[jira] [Updated] (AMBARI-22225) Cluster created using Blueprints rejects hosts even though their host_name matches host predicate

[ https://issues.apache.org/jira/browse/AMBARI-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-5: -- Attachment: AMBARI-5.b2.6.v1.patch > Cluster created using Blueprints rejects

[jira] [Updated] (AMBARI-22225) Cluster created using Blueprints rejects hosts even though their host_name matches host predicate

[ https://issues.apache.org/jira/browse/AMBARI-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-5: -- Status: Patch Available (was: In Progress) > Cluster created using Blueprints

[jira] [Updated] (AMBARI-22224) host and hostname built-in variables are not populated when performing Kerberos-related operations

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

[jira] [Created] (AMBARI-22226) RU: Downgrade is failed ZKFC

Nate Cole created AMBARI-6: -- Summary: RU: Downgrade is failed ZKFC Key: AMBARI-6 URL: https://issues.apache.org/jira/browse/AMBARI-6 Project: Ambari Issue Type: Bug

[jira] [Resolved] (AMBARI-22192) Setup an application server for hosting the AD System Manager

[ https://issues.apache.org/jira/browse/AMBARI-22192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-22192. -- Resolution: Fixed Pushed to branch-3.0-ams > Setup an application server for hosting

[jira] [Created] (AMBARI-22225) Cluster created using Blueprints rejects hosts even though their host_name matches host predicate

Sebastian Toader created AMBARI-5: - Summary: Cluster created using Blueprints rejects hosts even though their host_name matches host predicate Key: AMBARI-5 URL:

[jira] [Commented] (AMBARI-22196) Refactor non-stack cluster-env configs to cluster settings

[ https://issues.apache.org/jira/browse/AMBARI-22196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202470#comment-16202470 ] Swapan Shridhar commented on AMBARI-22196: -- {code:title=commit to

[jira] [Updated] (AMBARI-22224) host and hostname built-in variables are not populated when performing Kerberos-related operations

[ https://issues.apache.org/jira/browse/AMBARI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-4: -- Attachment: AMBARI-4_branch-2.6_01.patch AMBARI-4_trunk_01.patch >

[jira] [Updated] (AMBARI-22224) host and hostname built-in variables are not populated when performing Kerberos-related operations

[ https://issues.apache.org/jira/browse/AMBARI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-4: -- Status: Patch Available (was: In Progress) > host and hostname built-in variables are not

[jira] [Updated] (AMBARI-22149) SmartSense architecture pluggable for third party services

[ https://issues.apache.org/jira/browse/AMBARI-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-22149: --- Summary: SmartSense architecture pluggable for third party services (was: SmartSense

[jira] [Created] (AMBARI-22224) host and hostname built-in variables are not populated when performing Kerberos-related operations

Robert Levas created AMBARI-4: - Summary: host and hostname built-in variables are not populated when performing Kerberos-related operations Key: AMBARI-4 URL:

[jira] [Updated] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked

[ https://issues.apache.org/jira/browse/AMBARI-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-0: Attachment: AMBARI-0.patch > Should be able to switch the extension version to which a stack

[jira] [Updated] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked

[ https://issues.apache.org/jira/browse/AMBARI-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-0: Status: Patch Available (was: Open) > Should be able to switch the extension version to which a

[jira] [Created] (AMBARI-22223) Account for hive security, transport mode and SSL in zeppelin's jdbc interpreter setting

Kshitij Badani created AMBARI-3: --- Summary: Account for hive security, transport mode and SSL in zeppelin's jdbc interpreter setting Key: AMBARI-3 URL: https://issues.apache.org/jira/browse/AMBARI-3

[jira] [Updated] (AMBARI-22192) Setup an application server for hosting the AD System Manager

[ https://issues.apache.org/jira/browse/AMBARI-22192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22192: - Attachment: AMBARI-22192.patch > Setup an application server for hosting the AD System

[jira] [Updated] (AMBARI-22192) Setup an application server for hosting the AD System Manager

[ https://issues.apache.org/jira/browse/AMBARI-22192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22192: - Summary: Setup an application server for hosting the AD System Manager (was: Setup an

[jira] [Updated] (AMBARI-22180) [Modular Deployment][MVP] Download Configuration

[ https://issues.apache.org/jira/browse/AMBARI-22180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22180: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch received +1 on

[jira] [Updated] (AMBARI-22180) [Modular Deployment][MVP] Download Configuration

[ https://issues.apache.org/jira/browse/AMBARI-22180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-22180: - Fix Version/s: 3.0.0 > [Modular Deployment][MVP] Download Configuration >

[jira] [Updated] (AMBARI-22180) [Modular Deployment][MVP] Download Configuration

[ https://issues.apache.org/jira/browse/AMBARI-22180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22180: -- Status: Patch Available (was: Open) > [Modular Deployment][MVP] Download Configuration >

[jira] [Updated] (AMBARI-22163) Anomaly Storage: Design Metric anomalies schema.

[ https://issues.apache.org/jira/browse/AMBARI-22163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22163: --- Resolution: Fixed Status: Resolved (was: Patch Available) Checked in V1 of

[jira] [Updated] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk

[ https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-2: -- Attachment: AMBARI-2.patch > Switch druid to use /var/druid directory instead of

[jira] [Created] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk

Nishant Bangarwa created AMBARI-2: - Summary: Switch druid to use /var/druid directory instead of /apps/druid on local disk Key: AMBARI-2 URL: https://issues.apache.org/jira/browse/AMBARI-2

[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-1: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Druid Components

[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202300#comment-16202300 ] Nishant Bangarwa commented on AMBARI-1: --- committed to trunk and branch-2.6 > Druid

[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

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

[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202206#comment-16202206 ] Swapan Shridhar commented on AMBARI-1: -- +1 for patch. > Druid Components install fails

[jira] [Commented] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202143#comment-16202143 ] Nishant Bangarwa commented on AMBARI-1: --- this was a always a bug from the beginning, Got

[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-1: -- Status: Patch Available (was: Open) > Druid Components install fails with

[jira] [Updated] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-1: -- Attachment: AMBARI-1.patch > Druid Components install fails with AttributeError:

[jira] [Assigned] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa reassigned AMBARI-1: - Assignee: Nishant Bangarwa > Druid Components install fails with

[jira] [Created] (AMBARI-22221) Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos'

Dileep Kumar Chiguruvada created AMBARI-1: - Summary: Druid Components install fails with AttributeError: 'DruidBroker' object has no attribute 'available_packages_in_repos' Key: AMBARI-1 URL:

[jira] [Commented] (AMBARI-22219) Set current_version for Backward Compatibility

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

[jira] [Created] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked

Tim Thorpe created AMBARI-0: --- Summary: Should be able to switch the extension version to which a stack version is linked Key: AMBARI-0 URL: https://issues.apache.org/jira/browse/AMBARI-0

[jira] [Commented] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

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

[jira] [Resolved] (AMBARI-22219) Set current_version for Backward Compatibility

[ https://issues.apache.org/jira/browse/AMBARI-22219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-22219. -- Resolution: Fixed > Set current_version for Backward Compatibility >

[jira] [Updated] (AMBARI-22219) Set current_version for Backward Compatibility

[ https://issues.apache.org/jira/browse/AMBARI-22219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22219: - Attachment: AMBARI-22219.patch > Set current_version for Backward Compatibility >

[jira] [Updated] (AMBARI-22219) Set current_version for Backward Compatibility

[ https://issues.apache.org/jira/browse/AMBARI-22219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-22219: - Status: Patch Available (was: Open) > Set current_version for Backward Compatibility >

[jira] [Commented] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

[ https://issues.apache.org/jira/browse/AMBARI-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201996#comment-16201996 ] Andrii Babiichuk commented on AMBARI-22218: --- Committed to trunk > Log Search UI generated by

[jira] [Updated] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

[ https://issues.apache.org/jira/browse/AMBARI-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22218: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search UI

[jira] [Commented] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

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

[jira] [Commented] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

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

[jira] [Created] (AMBARI-22219) Set current_version for Backward Compatibility

Jonathan Hurley created AMBARI-22219: Summary: Set current_version for Backward Compatibility Key: AMBARI-22219 URL: https://issues.apache.org/jira/browse/AMBARI-22219 Project: Ambari

[jira] [Commented] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

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

[jira] [Commented] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

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

[jira] [Commented] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

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

[jira] [Updated] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

[ https://issues.apache.org/jira/browse/AMBARI-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22218: -- Attachment: AMBARI-22218.patch > Log Search UI generated by maven build uses mock

[jira] [Updated] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

[ https://issues.apache.org/jira/browse/AMBARI-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22218: -- Status: Patch Available (was: Open) > Log Search UI generated by maven build uses

[jira] [Commented] (AMBARI-22217) Deploy fails due to PU code related issues (post-merge)

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

[jira] [Updated] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

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

[jira] [Commented] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

[ https://issues.apache.org/jira/browse/AMBARI-22207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201901#comment-16201901 ] Andrii Tkach commented on AMBARI-22207: --- +1 for trunk patch > [Intermittent] While moving master,

[jira] [Commented] (AMBARI-22217) Deploy fails due to PU code related issues (post-merge)

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

[jira] [Created] (AMBARI-22218) Log Search UI generated by maven build uses mock data instead of real API

Andrii Babiichuk created AMBARI-22218: - Summary: Log Search UI generated by maven build uses mock data instead of real API Key: AMBARI-22218 URL: https://issues.apache.org/jira/browse/AMBARI-22218

[jira] [Commented] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

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

[jira] [Created] (AMBARI-22217) Deploy fails due to PU code related issues (post-merge)

Andrew Onischuk created AMBARI-22217: Summary: Deploy fails due to PU code related issues (post-merge) Key: AMBARI-22217 URL: https://issues.apache.org/jira/browse/AMBARI-22217 Project: Ambari

[jira] [Updated] (AMBARI-22217) Deploy fails due to PU code related issues (post-merge)

[ https://issues.apache.org/jira/browse/AMBARI-22217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22217: - Status: Patch Available (was: Open) > Deploy fails due to PU code related issues

[jira] [Updated] (AMBARI-22217) Deploy fails due to PU code related issues (post-merge)

[ https://issues.apache.org/jira/browse/AMBARI-22217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22217: - Attachment: AMBARI-22217.patch > Deploy fails due to PU code related issues

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Affects Version/s: 2.6.0 > Ambari Schema Upgrade Failed during Ambari Upgrade >

[jira] [Commented] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

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

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Fix Version/s: 2.6.0 > Ambari Schema Upgrade Failed during Ambari Upgrade >

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Status: Patch Available (was: Open) > Non-root ambari user causes Express Upgrade to

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Attachment: (was: AMBARI-22187-branch-2.6.patch) > Non-root ambari user causes

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Attachment: AMBARI-22187-branch-2.6.0.patch > Non-root ambari user causes Express Upgrade

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Status: Open (was: Patch Available) > Non-root ambari user causes Express Upgrade to

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Attachment: AMBARI-22216.patch > Ambari Schema Upgrade Failed during Ambari

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Status: Patch Available (was: Open) > Ambari Schema Upgrade Failed during Ambari

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Attachment: AMBARI-22216.patch > Ambari Schema Upgrade Failed during Ambari

[jira] [Created] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

Dmitry Lysnichenko created AMBARI-22216: --- Summary: Ambari Schema Upgrade Failed during Ambari Upgrade Key: AMBARI-22216 URL: https://issues.apache.org/jira/browse/AMBARI-22216 Project: Ambari

[jira] [Updated] (AMBARI-22216) Ambari Schema Upgrade Failed during Ambari Upgrade

[ https://issues.apache.org/jira/browse/AMBARI-22216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22216: Component/s: ambari-server > Ambari Schema Upgrade Failed during Ambari Upgrade >

[jira] [Commented] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

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

[jira] [Updated] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

[ https://issues.apache.org/jira/browse/AMBARI-22207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22207: - Status: Patch Available (was: In Progress) > [Intermittent] While moving

[jira] [Updated] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

[ https://issues.apache.org/jira/browse/AMBARI-22207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22207: - Attachment: AMBARI-22207_trunk.patch > [Intermittent] While moving master, a

[jira] [Updated] (AMBARI-22207) [Intermittent] While moving master, a manual commands wizard came in between

[ https://issues.apache.org/jira/browse/AMBARI-22207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22207: - Status: In Progress (was: Patch Available) > [Intermittent] While moving

[jira] [Updated] (AMBARI-22212) Alter logic for storing interpreter.json

[ https://issues.apache.org/jira/browse/AMBARI-22212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22212: - Resolution: Fixed Fix Version/s: 2.6.0 3.0.0

[jira] [Updated] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

[ https://issues.apache.org/jira/browse/AMBARI-22214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22214: - Resolution: Fixed Fix Version/s: 2.6.0 3.0.0

[jira] [Commented] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

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

[jira] [Commented] (AMBARI-22213) "ambari-server upgrade" failed on db schema [Upgrade]

[ https://issues.apache.org/jira/browse/AMBARI-22213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201820#comment-16201820 ] Hudson commented on AMBARI-22213: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #372 (See

[jira] [Commented] (AMBARI-22212) Alter logic for storing interpreter.json

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

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Status: Patch Available (was: Open) > Non-root ambari user causes Express Upgrade to

[jira] [Updated] (AMBARI-22212) Alter logic for storing interpreter.json

[ https://issues.apache.org/jira/browse/AMBARI-22212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22212: - Attachment: AMBARI-22212_branch-2.6_v1.patch AMBARI-22212_trunk_v1.patch

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Attachment: AMBARI-22187-branch-2.6.patch > Non-root ambari user causes Express Upgrade

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Attachment: (was: AMBARI-22187_branch-2.6.patch) > Non-root ambari user causes

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Status: Open (was: Patch Available) > Non-root ambari user causes Express Upgrade to

[jira] [Updated] (AMBARI-22213) "ambari-server upgrade" failed on db schema [Upgrade]

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

[jira] [Commented] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

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

[jira] [Commented] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

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

[jira] [Resolved] (AMBARI-22215) Refine cluster second aggregator by aligning sink publish times to 1 minute boundaries.

[ https://issues.apache.org/jira/browse/AMBARI-22215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-22215. - Resolution: Fixed Committed to branch-3.0-ams > Refine cluster second aggregator by aligning

[jira] [Created] (AMBARI-22215) Refine cluster second aggregator by aligning sink publish times to 1 minute boundaries.

Dmytro Sen created AMBARI-22215: --- Summary: Refine cluster second aggregator by aligning sink publish times to 1 minute boundaries. Key: AMBARI-22215 URL: https://issues.apache.org/jira/browse/AMBARI-22215

[jira] [Commented] (AMBARI-22204) Updating Ranger Admin pre-upgrade task

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

[jira] [Updated] (AMBARI-22214) Livy protocol to be set to https in Zeppelin's interpreter setting

[ https://issues.apache.org/jira/browse/AMBARI-22214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22214: - Attachment: AMBARI-22214_trunk_v2.patch > Livy protocol to be set to https in

[jira] [Updated] (AMBARI-22204) Updating Ranger Admin pre-upgrade task

[ https://issues.apache.org/jira/browse/AMBARI-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22204: - Attachment: AMBARI-22204.1.patch AMBARI-22204-1-trunk.patch > Updating

[jira] [Updated] (AMBARI-22187) Non-root ambari user causes Express Upgrade to fail during checking HDFS safe mode phase

[ https://issues.apache.org/jira/browse/AMBARI-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piyush Chavhan updated AMBARI-22187: Status: Patch Available (was: In Progress) > Non-root ambari user causes Express Upgrade

  1   2   >