[jira] [Updated] (AMBARI-15933) Views work for Hue to Views Migration Tool
[ https://issues.apache.org/jira/browse/AMBARI-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradarttana updated AMBARI-15933: - Attachment: AMBARI-15933.2_trunk.patch > Views work for Hue to Views Migration Tool > -- > > Key: AMBARI-15933 > URL: https://issues.apache.org/jira/browse/AMBARI-15933 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: ambari-2.4.0 > Environment: Hue is only supported on Linux (non HDInsight), hence > whever Hue was previously supported on we must be able to migrate. >Reporter: Pradarttana >Priority: Critical > Labels: ambari-views, dev-test, scoping > Fix For: ambari-2.4.0 > > Attachments: AMBARI-15933.1_trunk.patch, AMBARI-15933.2_trunk.patch, > AMBARI-15933_trunk.patch > > Original Estimate: 840h > Remaining Estimate: 840h > > Problem: Hue is planned to be deprecated, hence need a way for customers to > migrate over artifacts from Hue to the equivalent Views. > Link to the PRD Doc > https://docs.google.com/a/hortonworks.com/document/d/13m-Ioxamq4oF3yYHASkVjJ3mhpRlKuM12BCgCAJaap4/edit?usp=sharing > This RMP is a clone specifically to cover the work on the Views Framework > side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-16024: --- Assignee: bhuvnesh chaudhary > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
bhuvnesh chaudhary created AMBARI-16024: --- Summary: Remove performing service check during "Remove Standby Wizard" Key: AMBARI-16024 URL: https://issues.apache.org/jira/browse/AMBARI-16024 Project: Ambari Issue Type: Bug Reporter: bhuvnesh chaudhary Attachments: AMBARI-16024.patch Users will need to remove the HAWQ Standby Master using "Remove Standby Wizard" after enabling HDFS HA. So the service check may fail during the wizard as the HAWQ catalog might be still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Attachment: AMBARI-16024.patch > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16024: Status: Patch Available (was: Open) > Remove performing service check during "Remove Standby Wizard" > -- > > Key: AMBARI-16024 > URL: https://issues.apache.org/jira/browse/AMBARI-16024 > Project: Ambari > Issue Type: Bug >Reporter: bhuvnesh chaudhary > Attachments: AMBARI-16024.patch > > > Users will need to remove the HAWQ Standby Master using "Remove Standby > Wizard" after enabling HDFS HA. > So the service check may fail during the wizard as the HAWQ catalog might be > still pointing to the old filespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Status: Patch Available (was: Open) > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Status: Open (was: Patch Available) > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Attachment: AMBARI-15892-2.patch > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Attachment: (was: AMBARI-15892-2.patch) > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16021) Update LogSearch integration to use configuration to obtain credential
[ https://issues.apache.org/jira/browse/AMBARI-16021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton updated AMBARI-16021: -- Status: Patch Available (was: In Progress) > Update LogSearch integration to use configuration to obtain credential > -- > > Key: AMBARI-16021 > URL: https://issues.apache.org/jira/browse/AMBARI-16021 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16021.patch > > > The LogSearch integration components in Ambari needs to obtain the credential > used to connect to the LogSearch service via a configuration mechanism. > In the initial checkins, the integration code used a hard-coded credential. > Now that AMBARI-15884 has implemented the stack and configuration support to > allow a user to configure the credential for the LogSearch Server, the Ambari > Integration layer should use this configuration, defined in: > ambari/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-admin-properties.xml > This current JIRA tracks the work involved in updating the integration layer > to obtain the credential from the cluster's configuration, and use this > credential to connect to the LogSearch service. > I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16021) Update LogSearch integration to use configuration to obtain credential
[ https://issues.apache.org/jira/browse/AMBARI-16021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton updated AMBARI-16021: -- Attachment: AMBARI-16021.patch Uploaded initial version of patch > Update LogSearch integration to use configuration to obtain credential > -- > > Key: AMBARI-16021 > URL: https://issues.apache.org/jira/browse/AMBARI-16021 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16021.patch > > > The LogSearch integration components in Ambari needs to obtain the credential > used to connect to the LogSearch service via a configuration mechanism. > In the initial checkins, the integration code used a hard-coded credential. > Now that AMBARI-15884 has implemented the stack and configuration support to > allow a user to configure the credential for the LogSearch Server, the Ambari > Integration layer should use this configuration, defined in: > ambari/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-admin-properties.xml > This current JIRA tracks the work involved in updating the integration layer > to obtain the credential from the cluster's configuration, and use this > credential to connect to the LogSearch service. > I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15519) Add Service Wizard with nodes in the maintenance mode
[ https://issues.apache.org/jira/browse/AMBARI-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15519: Status: Patch Available (was: Reopened) > Add Service Wizard with nodes in the maintenance mode > - > > Key: AMBARI-15519 > URL: https://issues.apache.org/jira/browse/AMBARI-15519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-15519.amend.v0.patch, AMBARI-15519.v0.patch > > > On the cluster where some nodes are in the maintenance mode Add Service > Wizard doesn't track this. > So, user may select host in the maintenance mode to install some master > component. And this component won't be installed (only record in the DB will > be created for it). > Another situation: > there is some cluster where all nodes are in the maintenance mode. In this > case ASW is almost useless. Because all new components won't be installed > while it works. > Maybe ASW should track hosts in the maintenance mode and warn user about > adding components on them (Steps "Assign Masters", "Assign Slaves and > Clients")? Or just don't allow to do this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15519) Add Service Wizard with nodes in the maintenance mode
[ https://issues.apache.org/jira/browse/AMBARI-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15519: Attachment: AMBARI-15519.amend.v0.patch Local ambari-web test passed. 27517 tests complete (23 seconds) 154 tests pending Manual testing done. > Add Service Wizard with nodes in the maintenance mode > - > > Key: AMBARI-15519 > URL: https://issues.apache.org/jira/browse/AMBARI-15519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-15519.amend.v0.patch, AMBARI-15519.v0.patch > > > On the cluster where some nodes are in the maintenance mode Add Service > Wizard doesn't track this. > So, user may select host in the maintenance mode to install some master > component. And this component won't be installed (only record in the DB will > be created for it). > Another situation: > there is some cluster where all nodes are in the maintenance mode. In this > case ASW is almost useless. Because all new components won't be installed > while it works. > Maybe ASW should track hosts in the maintenance mode and warn user about > adding components on them (Steps "Assign Masters", "Assign Slaves and > Clients")? Or just don't allow to do this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16003) JS error on hosts filtering when filter for same field is used twice
[
https://issues.apache.org/jira/browse/AMBARI-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-16003:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk 04f7d5c3efe8af2c43824f32c1ce04d2ddc6cee2
> JS error on hosts filtering when filter for same field is used twice
>
>
> Key: AMBARI-16003
> URL: https://issues.apache.org/jira/browse/AMBARI-16003
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-16003.patch
>
>
> * Open hosts page
> * Do filtering "Cores: 3" and "Cores: 1" in the same time
> * JS-error appears: {{Uncaught TypeError: value.charAt is not a function}}
> {code}
> getComparisonType: function (value) {
> var comparisonChar = value.charAt(0);
> var result = 'EQUAL';
> if (isNaN(comparisonChar)) {
> switch (comparisonChar) {
> case '>':
> result = 'MORE';
> break;
> case '<':
> result = 'LESS';
> break;
> }
> }
> return result;
> },
> {code}
> UI expects that {{value}} is a string and not an array of strings.
> Same issue is when filtering is done by RAM-field
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Affects Version/s: (was: 2.4.0) 2.2.2 > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-15519) Add Service Wizard with nodes in the maintenance mode
[ https://issues.apache.org/jira/browse/AMBARI-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reopened AMBARI-15519: - > Add Service Wizard with nodes in the maintenance mode > - > > Key: AMBARI-15519 > URL: https://issues.apache.org/jira/browse/AMBARI-15519 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-15519.v0.patch > > > On the cluster where some nodes are in the maintenance mode Add Service > Wizard doesn't track this. > So, user may select host in the maintenance mode to install some master > component. And this component won't be installed (only record in the DB will > be created for it). > Another situation: > there is some cluster where all nodes are in the maintenance mode. In this > case ASW is almost useless. Because all new components won't be installed > while it works. > Maybe ASW should track hosts in the maintenance mode and warn user about > adding components on them (Steps "Assign Masters", "Assign Slaves and > Clients")? Or just don't allow to do this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Attachment: AMBARI-16018_2.2.patch > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-16018_2.2.patch, AMBARI-16018_trunk.patch > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Attachment: AMBARI-16018_trunk.patch > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-16018_2.2.patch, AMBARI-16018_trunk.patch > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Status: Patch Available (was: Open) > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-16018_2.2.patch, AMBARI-16018_trunk.patch > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated AMBARI-16013:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed.
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v2.patch,
> AMBARI-16013.trunk.v2.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Fix Version/s: (was: 2.4.0) 2.2.2 > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16023) Auth-to-local rule generation duplicates default rules when adding case-insensitive default rules
Robert Levas created AMBARI-16023:
-
Summary: Auth-to-local rule generation duplicates default rules
when adding case-insensitive default rules
Key: AMBARI-16023
URL: https://issues.apache.org/jira/browse/AMBARI-16023
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.4.0
When re-generating auth-to-local rules where existing rules are already set,
the default (or fallback) rule for the default and additional realms is
duplicated but the extra instance(s) have the case-insensitive flag:
Example:
{noformat:title=Was}
...
RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*//
...
{noformat}
{noformat:title=Becomes}
...
RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*//
RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*///L
...
{noformat}
*Steps to Reproduce*
# Create cluster with (at least) HDFS
# Enable Kerberos (do not check the box next to "Enable case insensitive
username rules"; kerberos-env/case_insensitive_username_rules should be false
# Edit Kerberos configuration and check "Enable case insensitive username
rules" to set kerberos-env/case_insensitive_username_rules to true
# Regenerate Keytabs
# See duplicate entry in HDFS configs (core-site/hadoop.security.auth_to_local)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[ https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16019: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk, branch-2.2, branch-2.2.2 > Validation popup: Proceed Anyway button is disabled > --- > > Key: AMBARI-16019 > URL: https://issues.apache.org/jira/browse/AMBARI-16019 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-16019.patch, Screen Shot 2016-04-20 at 1.19.39 > PM.png, disdown.png, proceedDisabled.png > > > # Change configurations that will make validation API return validation issue > with atleatst one issue of any type except 'WARN' type. > # This will display popup to user with 'Cancel' and 'Proceed Anyway' button > 'Proceed Anyway' button is disabled. > One of possible ways to reproduce > STR: > # Install ambari 2.0.2 with HDP 2.2.8.0-3150 > # Add Ranger > # Turn on security (ambari-server setup-security) > # Kerberise cluster > # Upgrade ambari to 2.2.2.0 > # Try to add some services (e.g SmartSense) > Result: "Proceed Anyway" button is disabled on popup after "Configure > services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15657) HAWQ config should not allow multiple Master/Segment directories
[
https://issues.apache.org/jira/browse/AMBARI-15657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252401#comment-15252401
]
Antonenko Alexander commented on AMBARI-15657:
--
[~mithmatt], [~lavjain],
Hi, we faced issue that is related with this patch. Please see AMBARI-16019.
This is cased by two lines of code that was added in committed patch
// Do not allow "Proceed Anyway" for validation errors
disablePrimary: self.get('configValidationError'),
This may block users, or make them do unwanted changes to configs.
Please see patch for AMBARI-16019. The fix is simple, we remove this two lines.
Just wanted to let you know about that changes and please put more people for
review if you do such a fundamental changes.
> HAWQ config should not allow multiple Master/Segment directories
>
>
> Key: AMBARI-15657
> URL: https://issues.apache.org/jira/browse/AMBARI-15657
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk, 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Attachments: AMBARI-15657.branch22.patch, AMBARI-15657.patch,
> screenshot.png
>
>
> User can add multiple space delimited directories, but after installation, it
> shows a comma in between. however, only first directory goes into effect,
> that too with a comma in the end.
> {code}
> [pivotal@ip-10-32-36-213 etc]$ cat hawq-site.xml
>
> hawq_master_directory
> /data/hawq/master,/data/hawq/master2
>
>
> hawq_segment_directory
> /data/hawq/segment,/data/hawq/segment2
>
> [pivotal@ip-10-32-36-213 etc]$ ls -l /data/hawq
> drwxr-xr-x 3 root root 4096 Mar 12 01:00 master,
> drwxr-xr-x 3 root root 4096 Mar 12 01:00 segment,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15915) SQL constraints: Inline constraints and name them in CREATE table
[ https://issues.apache.org/jira/browse/AMBARI-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-15915: -- Resolution: Fixed Status: Resolved (was: Patch Available) > SQL constraints: Inline constraints and name them in CREATE table > - > > Key: AMBARI-15915 > URL: https://issues.apache.org/jira/browse/AMBARI-15915 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sebastian Toader >Assignee: Balázs Bence Sári > Fix For: 2.4.0 > > Attachments: patch2.diff > > > Move ALTER TABLE statements for unique and foreign key constraints into the > CREATE table statement. > Also provide primary key constraint names where primary keys are specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[
https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252383#comment-15252383
]
Hadoop QA commented on AMBARI-16019:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/1289/AMBARI-16019.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6584//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6584//console
This message is automatically generated.
> Validation popup: Proceed Anyway button is disabled
> ---
>
> Key: AMBARI-16019
> URL: https://issues.apache.org/jira/browse/AMBARI-16019
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16019.patch, Screen Shot 2016-04-20 at 1.19.39
> PM.png, disdown.png, proceedDisabled.png
>
>
> # Change configurations that will make validation API return validation issue
> with atleatst one issue of any type except 'WARN' type.
> # This will display popup to user with 'Cancel' and 'Proceed Anyway' button
> 'Proceed Anyway' button is disabled.
> One of possible ways to reproduce
> STR:
> # Install ambari 2.0.2 with HDP 2.2.8.0-3150
> # Add Ranger
> # Turn on security (ambari-server setup-security)
> # Kerberise cluster
> # Upgrade ambari to 2.2.2.0
> # Try to add some services (e.g SmartSense)
> Result: "Proceed Anyway" button is disabled on popup after "Configure
> services" step
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16022) Config group UI enhancements
Sangeeta Ravindran created AMBARI-16022: --- Summary: Config group UI enhancements Key: AMBARI-16022 URL: https://issues.apache.org/jira/browse/AMBARI-16022 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor 1. The drop-down listing config-groups seems to truncate the group name when the length exceeds 18. If the config group name is longer, the full name is invisible. The items in the drop-down list also show the partial truncated name. Having a tooltip would allow for the entire name to be displayed. 2. In Manage Config Groups, the Description field allows entry of special characters. Need to restrict characters since the description is stored in the Database. 3. Save Configuration Group dialog, the message spills outside the inner frame. Need to make the text wrap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16009) Regenerating keytabs on re-imaged hosts results in error during 'Creating Principals'
[
https://issues.apache.org/jira/browse/AMBARI-16009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16009:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 783b4d39213b5819037f4eb707754a32eb722b71
Author: Robert Levas
Date: Thu Apr 21 13:59:18 2016 -0400
{noformat}
Committed to branch-2.2
{noformat}
commit 7e7f3b0a8d60895ef52002ff54daff846602d52e
Author: Robert Levas
Date: Thu Apr 21 14:00:15 2016 -0400
{noformat}
Committed to branch-2.2.2
{noformat}
commit f4eeadbcea5f12104f96b7707344491ce59d7c95
Author: Robert Levas
Date: Thu Apr 21 14:01:20 2016 -0400
{noformat}
> Regenerating keytabs on re-imaged hosts results in error during 'Creating
> Principals'
> -
>
> Key: AMBARI-16009
> URL: https://issues.apache.org/jira/browse/AMBARI-16009
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos
> Fix For: 2.2.2
>
> Attachments: AMBARI-16009_branch-2.2_01.patch,
> AMBARI-16009_trunk_01.patch
>
>
> We had a 1600 unsecured cluster initially, from which 700 nodes were
> destroyed. Though Ambari-server knew of 1600 hosts, only 900 were
> heartbeating. At this point we secured the cluster and everything was good.
> Then we brought back the 700 hosts, which started heartbeating with
> ambari-server.
> At this point we did 'Regenerate Keytabs' which failed at the 'Create
> Principals' step (image attached), as it was trying to re-create principal
> which is already existing with kadmin, and with ambari-server.
> *Create Principals*
> Stderr:
> {noformat}
> 2016-04-21 01:28:52,985 - Failed to create or update principal,
> HTTP/host1.example@example.com - Failed to create service principal for
> HTTP/host1.example@example.com
> STDOUT: Authenticating as principal admin/admin with password.
> STDERR: WARNING: no policy specified for HTTP/host1.example@example.com;
> defaulting to no policy
> add_principal: Principal or policy already exists while creating
> "HTTP/host1.example@example.com".
> {noformat}
> Stdout:
> {noformat}
> 2016-04-21 01:27:32,400 - Processing identities...
> 2016-04-21 01:28:29,874 - Processing principal,
> HTTP/host1.example@example.com
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15752) Ambari support for additional config params for Ranger KMS to support HSM
[ https://issues.apache.org/jira/browse/AMBARI-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252346#comment-15252346 ] Hudson commented on AMBARI-15752: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-15752. Ambari support for additional config params for Ranger KMS (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8006d3d6a77615b43aeb619bac6231d9f3ff2b75]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/configuration/kms-env.xml * ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py * ambari-common/src/main/python/resource_management/libraries/functions/stack_features.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/themes/theme_version_2.json * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER_KMS/configuration/dbks-site.xml * ambari-common/src/main/python/resource_management/libraries/functions/constants.py > Ambari support for additional config params for Ranger KMS to support HSM > - > > Key: AMBARI-15752 > URL: https://issues.apache.org/jira/browse/AMBARI-15752 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0, ambari-2.4.0 > > Attachments: AMBARI-15752.1.patch, AMBARI-15752.2.patch, > AMBARI-15752.3.patch, AMBARI-15752.patch > > > Add HSM support configuration properties for Ranger KMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16011) Remove example AMS alert definitions from HDFS/alert.json
[ https://issues.apache.org/jira/browse/AMBARI-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252342#comment-15252342 ] Hudson commented on AMBARI-16011: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-16011 Remove example AMS alert definitions from HDFS/alert.json (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a6dadc3c25d33298865e1f0fec83624834c16c1]) * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json > Remove example AMS alert definitions from HDFS/alert.json > - > > Key: AMBARI-16011 > URL: https://issues.apache.org/jira/browse/AMBARI-16011 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16011.patch > > > Remove example AMS alert definitions from HDFS alert.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16001) Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1 upgrade
[
https://issues.apache.org/jira/browse/AMBARI-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252343#comment-15252343
]
Hudson commented on AMBARI-16001:
-
FAILURE: Integrated in Ambari-trunk-Commit #4706 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4706/])
AMBARI-16001. Fix bad entry in hbase-env.sh, added as part of (ajit:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc6cde341097308aca190b1dde38591f90108b17])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
> Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1 upgrade
> -
>
> Key: AMBARI-16001
> URL: https://issues.apache.org/jira/browse/AMBARI-16001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.2.2
>
> Attachments: rb45592.patch
>
>
> Ambari upgrades, 2.2.0-2.2.1.1 adds a bad entry to the hbase-env
> {code}export HBASE_OPTS="-Djava.io.tmpdir={{java_io_tmpdir}}"{code}
> With broken hbase-env user cannot run any mapreduce services for hbase.
> Currently it needs to be fixed manually.
> {code}
> export HBASE_OPTS="${HBASE_OPTS} -Djava.io.tmpdir={{java_io_tmpdir}}"
> {code}
> It will be good if just upgrading to 2.2.2 fixes this issue rather than
> mucking around with configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15915) SQL constraints: Inline constraints and name them in CREATE table
[ https://issues.apache.org/jira/browse/AMBARI-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252341#comment-15252341 ] Hudson commented on AMBARI-15915: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-15915. SQL constraints: Inline constraints and name them in (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=346dfe7eb78b8a71e4981c034fb2f3fddba0db81]) * ambari-server/src/test/java/org/apache/ambari/server/orm/db/DDLTestUtils.java * ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql * ambari-server/src/test/java/org/apache/ambari/server/orm/db/DDLTests.java * ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql > SQL constraints: Inline constraints and name them in CREATE table > - > > Key: AMBARI-15915 > URL: https://issues.apache.org/jira/browse/AMBARI-15915 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sebastian Toader >Assignee: Balázs Bence Sári > Fix For: 2.4.0 > > Attachments: patch2.diff > > > Move ALTER TABLE statements for unique and foreign key constraints into the > CREATE table statement. > Also provide primary key constraint names where primary keys are specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16014) ambari-agent.log gets flooded up with exceptions from status commands
[ https://issues.apache.org/jira/browse/AMBARI-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252344#comment-15252344 ] Hudson commented on AMBARI-16014: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-16014. ambari-agent.log gets flooded up with exceptions from (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9be2ba28880dd7a87d3bd246d9566f0f745ce6c2]) * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat_client.py * ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/knox_gateway.py * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/rest_api.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py * ambari-server/src/main/resources/common-services/PIG/0.12.0.2.0/package/scripts/pig_client.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py * ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/accumulo_script.py * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_client.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/params.py * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_client.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/status_params.py * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/nimbus.py * ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/service_check.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py * ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume_handler.py * ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/job_history_server.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_service.py * ambari-server/src/main/resources/common-services/MAHOUT/1.0.0.2.3/package/scripts/mahout_client.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/nodemanager.py * ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py * ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/status_params.py * ambari-server/src/main/reso
[jira] [Commented] (AMBARI-15995) ambari upgrade fail (upgrade of ambari packages ... not hdp (eu/standard) upgrade)
[ https://issues.apache.org/jira/browse/AMBARI-15995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252345#comment-15252345 ] Hudson commented on AMBARI-15995: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-15995 ambari upgrade fail (upgrade of ambari packages ... not hdp (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8416c0df87282329be143cca13b5bbfc62e630c8]) * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java > ambari upgrade fail (upgrade of ambari packages ... not hdp (eu/standard) > upgrade) > -- > > Key: AMBARI-15995 > URL: https://issues.apache.org/jira/browse/AMBARI-15995 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-15995.patch > > > Ambari packages upgrade to 2.4.0.0.160. It fails at stage of upgrading ambari > database. > Step of failure > ambari-server upgrade. > 1. It complains about following > [root@host]# ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Can not find ambari.properties.rpmsave file from previous version, > skipping import of settings > WARNING: Can not find ambari-env.sh.rpmsave file from previous version, > skipping restore of environment settings > Fixing database objects owner > Ambari Server configured for Embedded Postgres. Confirm you have made a > backup of the Ambari Server database [y/n] (y)? y > Upgrading database schema > WARNING: Multiple versions of javax.servlet.jsp.jstl.jar found in java class > path (/usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.2.jar and > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar). > Make sure that you include only one javax.servlet.jsp.jstl.jar in the java > class path > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar'. > So I rename > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar to > something else and kept only > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.2.jar > 2. After above changes ambari-server upgrade does finishes but throws > following error when trying to start ambari-server. > 06 Apr 2016 15:29:17,518 ERROR [main] AmbariServer:930 - Failed to run the > Ambari Server > javax.persistence.PersistenceException: Exception [EclipseLink-116] (Eclipse > Persistence Services - 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: No conversion value provided for the value [UPGRADED] > in field [host_version.state]. > Mapping: > org.eclipse.persistence.mappings.DirectToFieldMapping[state-->host_version.state] > Descriptor: > RelationalDescriptor(org.apache.ambari.server.orm.entities.HostVersionEntity > --> [DatabaseTable(host_version)]) > at > org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:484) > at org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:62) > at org.apache.ambari.server.orm.dao.CrudDAO.findAll(CrudDAO.java:72) > at > org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:43) > at > org.apache.ambari.server.StateRecoveryManager.checkHostAndClusterVersions(StateRecoveryManager.java:53) > at > org.apache.ambari.server.StateRecoveryManager.doWork(StateRecoveryManager.java:48) > at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:595) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:928) > Caused by: Exception [EclipseLink-116] (Eclipse Persistence Services - > 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: No conversion value provided for the value [UPGRADED] > in field [host_version.state]. > Mapping: > org.eclipse.persistence.mappings.DirectToFieldMapping[state-->host_version.state] > Descriptor: > RelationalDescriptor(org.apache.ambari.server.orm.entities.HostVersionEntity > --> [DatabaseTable(host_version)]) > at > org.eclipse.persistence.exceptions.DescriptorException.noFieldValueConversionToAttributeValueProvided(DescriptorException.java:1066) > at > org.eclipse.persistence.mappings.converters.ObjectTypeConverter.convertDataValueToObjectValue(ObjectTypeConverter.java:226) > at > org.eclipse.persistence.mappings.converters.EnumTypeConverter.convertDataValueToObjectValue(EnumTypeConverter.java:141) > at > or
[jira] [Commented] (AMBARI-16008) Restart Phoenix Query Server intermittently fails on SLES 11 SP3
[ https://issues.apache.org/jira/browse/AMBARI-16008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252347#comment-15252347 ] Hudson commented on AMBARI-16008: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-16008. Restart Phoenix Query Server intermittently fails on SLES (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e46135ba1166da28321ad092c2207b570b6f83f]) * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/phoenix_service.py > Restart Phoenix Query Server intermittently fails on SLES 11 SP3 > > > Key: AMBARI-16008 > URL: https://issues.apache.org/jira/browse/AMBARI-16008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0, 2.2.2 > > Attachments: AMBARI-16008.patch > > > Phoenix query server intermittently fails on removing the PID file for SUSE > 11sp3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16006) Add logging to check_host.py
[ https://issues.apache.org/jira/browse/AMBARI-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252340#comment-15252340 ] Hudson commented on AMBARI-16006: - FAILURE: Integrated in Ambari-trunk-Commit #4706 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4706/]) AMBARI-16006. Add logging to check_host.py (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2adf08faa41dc9bfd602186585f026cb977858a3]) * ambari-server/src/main/resources/custom_actions/scripts/check_host.py * ambari-server/src/test/python/custom_actions/TestCheckHost.py > Add logging to check_host.py > > > Key: AMBARI-16006 > URL: https://issues.apache.org/jira/browse/AMBARI-16006 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16006.patch > > > Sometimes host check after host registration lasted too long (more than 720 > sec.). I's affect some system tests. I can't reproduce this, so it would be > good to add logging to this operation. > Currently, all the host check logs available are > > > > [root@c6404 data]# cat /var/lib/ambari-agent/data/output-3.txt > Last Agent Env check started. > Last Agent Env check completed successfully. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252326#comment-15252326
]
Hadoop QA commented on AMBARI-16020:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12800013/AMBARI-16020.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6583//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6583//console
This message is automatically generated.
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16020.patch
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16008) Restart Phoenix Query Server intermittently fails on SLES 11 SP3
[ https://issues.apache.org/jira/browse/AMBARI-16008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252310#comment-15252310 ] Hudson commented on AMBARI-16008: - SUCCESS: Integrated in Ambari-branch-2.2 #657 (See [https://builds.apache.org/job/Ambari-branch-2.2/657/]) AMBARI-16008. Restart Phoenix Query Server intermittently fails on SLES (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b4bf253c98d503f389114832fed1a89ac0a1b5eb]) * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/phoenix_service.py > Restart Phoenix Query Server intermittently fails on SLES 11 SP3 > > > Key: AMBARI-16008 > URL: https://issues.apache.org/jira/browse/AMBARI-16008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0, 2.2.2 > > Attachments: AMBARI-16008.patch > > > Phoenix query server intermittently fails on removing the PID file for SUSE > 11sp3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[
https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252295#comment-15252295
]
Hadoop QA commented on AMBARI-16012:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799968/AMBARI-16012.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6582//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6582//console
This message is automatically generated.
> JS error logged in dev console on signing in to ambari
> --
>
> Key: AMBARI-16012
> URL: https://issues.apache.org/jira/browse/AMBARI-16012
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41
> AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png
>
>
> *STR:*
> # Deploy a cluster with HDFS and YARN
> # Log off from ambari
> # Refresh browser
> # Log in to Ambari
> JS error as shown in attachment is generated.
> This issue happens intermittently with the stated STR as this seems to be
> timing issue. It seems that multiple quick links widgets on dashboard page
> are calling
> [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223]
> and this generates error at
> [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569]
> I haven't verified but this issue might affect http/https formation in quick
> link structure of dashboard widget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-16020:
--
Attachment: AMBARI-16020.patch
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16020.patch
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-16020:
--
Status: Patch Available (was: Open)
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16020.patch
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[ https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252277#comment-15252277 ] Andrii Tkach commented on AMBARI-16019: --- +1 for the patch > Validation popup: Proceed Anyway button is disabled > --- > > Key: AMBARI-16019 > URL: https://issues.apache.org/jira/browse/AMBARI-16019 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-16019.patch, Screen Shot 2016-04-20 at 1.19.39 > PM.png, disdown.png, proceedDisabled.png > > > # Change configurations that will make validation API return validation issue > with atleatst one issue of any type except 'WARN' type. > # This will display popup to user with 'Cancel' and 'Proceed Anyway' button > 'Proceed Anyway' button is disabled. > One of possible ways to reproduce > STR: > # Install ambari 2.0.2 with HDP 2.2.8.0-3150 > # Add Ranger > # Turn on security (ambari-server setup-security) > # Kerberise cluster > # Upgrade ambari to 2.2.2.0 > # Try to add some services (e.g SmartSense) > Result: "Proceed Anyway" button is disabled on popup after "Configure > services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252274#comment-15252274
]
Andrii Tkach commented on AMBARI-16020:
---
27517 tests complete (27 seconds)
154 tests pending
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16021) Update LogSearch integration to use configuration to obtain credential
Robert Nettleton created AMBARI-16021: - Summary: Update LogSearch integration to use configuration to obtain credential Key: AMBARI-16021 URL: https://issues.apache.org/jira/browse/AMBARI-16021 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Robert Nettleton Assignee: Robert Nettleton Priority: Critical Fix For: 2.4.0 The LogSearch integration components in Ambari needs to obtain the credential used to connect to the LogSearch service via a configuration mechanism. In the initial checkins, the integration code used a hard-coded credential. Now that AMBARI-15884 has implemented the stack and configuration support to allow a user to configure the credential for the LogSearch Server, the Ambari Integration layer should use this configuration, defined in: ambari/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-admin-properties.xml This current JIRA tracks the work involved in updating the integration layer to obtain the credential from the cluster's configuration, and use this credential to connect to the LogSearch service. I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[ https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16019: - Status: Patch Available (was: Open) > Validation popup: Proceed Anyway button is disabled > --- > > Key: AMBARI-16019 > URL: https://issues.apache.org/jira/browse/AMBARI-16019 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-16019.patch, Screen Shot 2016-04-20 at 1.19.39 > PM.png, disdown.png, proceedDisabled.png > > > # Change configurations that will make validation API return validation issue > with atleatst one issue of any type except 'WARN' type. > # This will display popup to user with 'Cancel' and 'Proceed Anyway' button > 'Proceed Anyway' button is disabled. > One of possible ways to reproduce > STR: > # Install ambari 2.0.2 with HDP 2.2.8.0-3150 > # Add Ranger > # Turn on security (ambari-server setup-security) > # Kerberise cluster > # Upgrade ambari to 2.2.2.0 > # Try to add some services (e.g SmartSense) > Result: "Proceed Anyway" button is disabled on popup after "Configure > services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16010) Update HDFS HA alerts definitions during upgrade
[
https://issues.apache.org/jira/browse/AMBARI-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252256#comment-15252256
]
Hadoop QA commented on AMBARI-16010:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799960/AMBARI-16010.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6580//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6580//console
This message is automatically generated.
> Update HDFS HA alerts definitions during upgrade
>
>
> Key: AMBARI-16010
> URL: https://issues.apache.org/jira/browse/AMBARI-16010
> Project: Ambari
> Issue Type: Bug
> Components: alerts, ambari-upgrade
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16010.patch
>
>
> During upgrade hdfs-site/dfs.nameservices should be replaced with
> hdfs-site/dfs.internal.nameservices for all HDFS alerts.
> hdfs-site/dfs.nameservices might contain external nameservices
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
Andrii Tkach created AMBARI-16020:
-
Summary: Hive Metastore install failed since mysql-server not
installed
Key: AMBARI-16020
URL: https://issues.apache.org/jira/browse/AMBARI-16020
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
Fix For: 2.4.0
STR:
* Install Ambari 2.4.0.0-4686 on 3 hosts
* Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
other
* Select option to install Hive with "New MySQL" database
Failed installing Hive Metastore since MySQL service was not installed.
{code}
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 293, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'export
HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
/usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
-userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
launch YARN applications.
Metastore connection URL:
jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
Metastore Connection Driver :com.mysql.jdbc.Driver
Metastore connection User: hive
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
version.
*** schemaTool failed ***
{code}
I had to run this manually,
{code}
yum install mysql-server -y
service mysqld start
mysql -u root -p (password is empty string)
mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
IDENTIFIED BY 'admin' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
{code}
and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[ https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16019: - Attachment: AMBARI-16019.patch > Validation popup: Proceed Anyway button is disabled > --- > > Key: AMBARI-16019 > URL: https://issues.apache.org/jira/browse/AMBARI-16019 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-16019.patch, Screen Shot 2016-04-20 at 1.19.39 > PM.png, disdown.png, proceedDisabled.png > > > # Change configurations that will make validation API return validation issue > with atleatst one issue of any type except 'WARN' type. > # This will display popup to user with 'Cancel' and 'Proceed Anyway' button > 'Proceed Anyway' button is disabled. > One of possible ways to reproduce > STR: > # Install ambari 2.0.2 with HDP 2.2.8.0-3150 > # Add Ranger > # Turn on security (ambari-server setup-security) > # Kerberise cluster > # Upgrade ambari to 2.2.2.0 > # Try to add some services (e.g SmartSense) > Result: "Proceed Anyway" button is disabled on popup after "Configure > services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
[ https://issues.apache.org/jira/browse/AMBARI-16019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16019: - Attachment: disdown.png proceedDisabled.png Screen Shot 2016-04-20 at 1.19.39 PM.png > Validation popup: Proceed Anyway button is disabled > --- > > Key: AMBARI-16019 > URL: https://issues.apache.org/jira/browse/AMBARI-16019 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.2.2 > > Attachments: Screen Shot 2016-04-20 at 1.19.39 PM.png, disdown.png, > proceedDisabled.png > > > # Change configurations that will make validation API return validation issue > with atleatst one issue of any type except 'WARN' type. > # This will display popup to user with 'Cancel' and 'Proceed Anyway' button > 'Proceed Anyway' button is disabled. > One of possible ways to reproduce > STR: > # Install ambari 2.0.2 with HDP 2.2.8.0-3150 > # Add Ranger > # Turn on security (ambari-server setup-security) > # Kerberise cluster > # Upgrade ambari to 2.2.2.0 > # Try to add some services (e.g SmartSense) > Result: "Proceed Anyway" button is disabled on popup after "Configure > services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16019) Validation popup: Proceed Anyway button is disabled
Antonenko Alexander created AMBARI-16019: Summary: Validation popup: Proceed Anyway button is disabled Key: AMBARI-16019 URL: https://issues.apache.org/jira/browse/AMBARI-16019 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.2 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Blocker Fix For: 2.2.2 # Change configurations that will make validation API return validation issue with atleatst one issue of any type except 'WARN' type. # This will display popup to user with 'Cancel' and 'Proceed Anyway' button 'Proceed Anyway' button is disabled. One of possible ways to reproduce STR: # Install ambari 2.0.2 with HDP 2.2.8.0-3150 # Add Ranger # Turn on security (ambari-server setup-security) # Kerberise cluster # Upgrade ambari to 2.2.2.0 # Try to add some services (e.g SmartSense) Result: "Proceed Anyway" button is disabled on popup after "Configure services" step -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
[ https://issues.apache.org/jira/browse/AMBARI-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16018: - Description: - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). - 3 node, hdfs, yarn, zk, ams - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' The cluster has been running for close to an hour and these metrics are still not showing up. was: - I did an Ambari 2.4.0 install (build #193) of HDP 2.4.0 (GA). - 3 node, hdfs, yarn, zk, ams - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' The cluster has been running for close to an hour and these metrics are still not showing up. > Namenode RPC widget on Ambari Dashboard shows n/a > - > > Key: AMBARI-16018 > URL: https://issues.apache.org/jira/browse/AMBARI-16018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > > - I did an Ambari 2.4.0 install of HDP 2.4.0 (GA). > - 3 node, hdfs, yarn, zk, ams > - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' > The cluster has been running for close to an hour and these metrics are still > not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16018) Namenode RPC widget on Ambari Dashboard shows n/a
Antonenko Alexander created AMBARI-16018: Summary: Namenode RPC widget on Ambari Dashboard shows n/a Key: AMBARI-16018 URL: https://issues.apache.org/jira/browse/AMBARI-16018 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.4.0 - I did an Ambari 2.4.0 install (build #193) of HDP 2.4.0 (GA). - 3 node, hdfs, yarn, zk, ams - Ambari Web > Dashboard > NameNode RPC widget says 'n/a' The cluster has been running for close to an hour and these metrics are still not showing up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16009) Regenerating keytabs on re-imaged hosts results in error during 'Creating Principals'
[
https://issues.apache.org/jira/browse/AMBARI-16009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16009:
--
Attachment: AMBARI-16009_trunk_01.patch
AMBARI-16009_branch-2.2_01.patch
> Regenerating keytabs on re-imaged hosts results in error during 'Creating
> Principals'
> -
>
> Key: AMBARI-16009
> URL: https://issues.apache.org/jira/browse/AMBARI-16009
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos
> Fix For: 2.2.2
>
> Attachments: AMBARI-16009_branch-2.2_01.patch,
> AMBARI-16009_trunk_01.patch
>
>
> We had a 1600 unsecured cluster initially, from which 700 nodes were
> destroyed. Though Ambari-server knew of 1600 hosts, only 900 were
> heartbeating. At this point we secured the cluster and everything was good.
> Then we brought back the 700 hosts, which started heartbeating with
> ambari-server.
> At this point we did 'Regenerate Keytabs' which failed at the 'Create
> Principals' step (image attached), as it was trying to re-create principal
> which is already existing with kadmin, and with ambari-server.
> *Create Principals*
> Stderr:
> {noformat}
> 2016-04-21 01:28:52,985 - Failed to create or update principal,
> HTTP/host1.example@example.com - Failed to create service principal for
> HTTP/host1.example@example.com
> STDOUT: Authenticating as principal admin/admin with password.
> STDERR: WARNING: no policy specified for HTTP/host1.example@example.com;
> defaulting to no policy
> add_principal: Principal or policy already exists while creating
> "HTTP/host1.example@example.com".
> {noformat}
> Stdout:
> {noformat}
> 2016-04-21 01:27:32,400 - Processing identities...
> 2016-04-21 01:28:29,874 - Processing principal,
> HTTP/host1.example@example.com
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16009) Regenerating keytabs on re-imaged hosts results in error during 'Creating Principals'
[
https://issues.apache.org/jira/browse/AMBARI-16009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16009:
--
Status: Patch Available (was: In Progress)
> Regenerating keytabs on re-imaged hosts results in error during 'Creating
> Principals'
> -
>
> Key: AMBARI-16009
> URL: https://issues.apache.org/jira/browse/AMBARI-16009
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos
> Fix For: 2.2.2
>
> Attachments: AMBARI-16009_branch-2.2_01.patch,
> AMBARI-16009_trunk_01.patch
>
>
> We had a 1600 unsecured cluster initially, from which 700 nodes were
> destroyed. Though Ambari-server knew of 1600 hosts, only 900 were
> heartbeating. At this point we secured the cluster and everything was good.
> Then we brought back the 700 hosts, which started heartbeating with
> ambari-server.
> At this point we did 'Regenerate Keytabs' which failed at the 'Create
> Principals' step (image attached), as it was trying to re-create principal
> which is already existing with kadmin, and with ambari-server.
> *Create Principals*
> Stderr:
> {noformat}
> 2016-04-21 01:28:52,985 - Failed to create or update principal,
> HTTP/host1.example@example.com - Failed to create service principal for
> HTTP/host1.example@example.com
> STDOUT: Authenticating as principal admin/admin with password.
> STDERR: WARNING: no policy specified for HTTP/host1.example@example.com;
> defaulting to no policy
> add_principal: Principal or policy already exists while creating
> "HTTP/host1.example@example.com".
> {noformat}
> Stdout:
> {noformat}
> 2016-04-21 01:27:32,400 - Processing identities...
> 2016-04-21 01:28:29,874 - Processing principal,
> HTTP/host1.example@example.com
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16017) Update Moment.js to latest stable version 2.13.0
Sangeeta Ravindran created AMBARI-16017: --- Summary: Update Moment.js to latest stable version 2.13.0 Key: AMBARI-16017 URL: https://issues.apache.org/jira/browse/AMBARI-16017 Project: Ambari Issue Type: Task Components: ambari-views, ambari-web Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran The latest stable version of Moment.js is 2.13.0. This task is for updating the version of Moment.js used in contrib/views/slider/src/main/resources/ui/vendor/scripts/common/ ambari-web/vendor/scripts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16016) Properly handle 'properties' in Manage Config Group popup
[ https://issues.apache.org/jira/browse/AMBARI-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252155#comment-15252155 ] Aleksandr Kovalenko commented on AMBARI-16016: -- +1 for the patch > Properly handle 'properties' in Manage Config Group popup > - > > Key: AMBARI-16016 > URL: https://issues.apache.org/jira/browse/AMBARI-16016 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16516.patch > > > On installer on ASW > - create new override > - update value for this override > - open manage group popup > - select group that just was edited > - see 'properties' > value in 'properties' and override value doesn't match -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16015) Popup for selecting Hive Interactive host does not work after re-enabling the Interactive Query toggle
[ https://issues.apache.org/jira/browse/AMBARI-16015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252154#comment-15252154 ] Aleksandr Kovalenko commented on AMBARI-16015: -- +1 for the patch > Popup for selecting Hive Interactive host does not work after re-enabling the > Interactive Query toggle > -- > > Key: AMBARI-16015 > URL: https://issues.apache.org/jira/browse/AMBARI-16015 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16515.patch > > > *STR* > * During Install Wizard, choose HDP 2.5 > * Turn on "Enable Interactive Query" from Customize Services > Hive > Config > page. > * When prompted, select a host for Hive Interactive > * Undo "Enable Interactive Query" > * Turn "Enable Interactive Query" back on > * The host selection popup does not show the layout correctly (only shows > Hive Interactive - it originally showed all master assignments) > * Choose a different host for Hive Interactive > * "HiveServer2" interactive host does not reflect the user selection (shows > the original selection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16015) Popup for selecting Hive Interactive host does not work after re-enabling the Interactive Query toggle
[ https://issues.apache.org/jira/browse/AMBARI-16015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16015: -- Status: Patch Available (was: Open) 25681 tests complete (22 seconds) 154 tests pending > Popup for selecting Hive Interactive host does not work after re-enabling the > Interactive Query toggle > -- > > Key: AMBARI-16015 > URL: https://issues.apache.org/jira/browse/AMBARI-16015 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16515.patch > > > *STR* > * During Install Wizard, choose HDP 2.5 > * Turn on "Enable Interactive Query" from Customize Services > Hive > Config > page. > * When prompted, select a host for Hive Interactive > * Undo "Enable Interactive Query" > * Turn "Enable Interactive Query" back on > * The host selection popup does not show the layout correctly (only shows > Hive Interactive - it originally showed all master assignments) > * Choose a different host for Hive Interactive > * "HiveServer2" interactive host does not reflect the user selection (shows > the original selection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16016) Properly handle 'properties' in Manage Config Group popup
[ https://issues.apache.org/jira/browse/AMBARI-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16016: -- Status: Patch Available (was: Open) 25681 tests complete (22 seconds) 154 tests pending > Properly handle 'properties' in Manage Config Group popup > - > > Key: AMBARI-16016 > URL: https://issues.apache.org/jira/browse/AMBARI-16016 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16516.patch > > > On installer on ASW > - create new override > - update value for this override > - open manage group popup > - select group that just was edited > - see 'properties' > value in 'properties' and override value doesn't match -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16016) Properly handle 'properties' in Manage Config Group popup
[ https://issues.apache.org/jira/browse/AMBARI-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16016: -- Attachment: AMBARI-16516.patch > Properly handle 'properties' in Manage Config Group popup > - > > Key: AMBARI-16016 > URL: https://issues.apache.org/jira/browse/AMBARI-16016 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16516.patch > > > On installer on ASW > - create new override > - update value for this override > - open manage group popup > - select group that just was edited > - see 'properties' > value in 'properties' and override value doesn't match -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16015) Popup for selecting Hive Interactive host does not work after re-enabling the Interactive Query toggle
[ https://issues.apache.org/jira/browse/AMBARI-16015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16015: -- Attachment: AMBARI-16515.patch > Popup for selecting Hive Interactive host does not work after re-enabling the > Interactive Query toggle > -- > > Key: AMBARI-16015 > URL: https://issues.apache.org/jira/browse/AMBARI-16015 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16515.patch > > > *STR* > * During Install Wizard, choose HDP 2.5 > * Turn on "Enable Interactive Query" from Customize Services > Hive > Config > page. > * When prompted, select a host for Hive Interactive > * Undo "Enable Interactive Query" > * Turn "Enable Interactive Query" back on > * The host selection popup does not show the layout correctly (only shows > Hive Interactive - it originally showed all master assignments) > * Choose a different host for Hive Interactive > * "HiveServer2" interactive host does not reflect the user selection (shows > the original selection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16016) Properly handle 'properties' in Manage Config Group popup
Andrii Babiichuk created AMBARI-16016: - Summary: Properly handle 'properties' in Manage Config Group popup Key: AMBARI-16016 URL: https://issues.apache.org/jira/browse/AMBARI-16016 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.4.0 On installer on ASW - create new override - update value for this override - open manage group popup - select group that just was edited - see 'properties' value in 'properties' and override value doesn't match -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16015) Popup for selecting Hive Interactive host does not work after re-enabling the Interactive Query toggle
Andrii Babiichuk created AMBARI-16015: - Summary: Popup for selecting Hive Interactive host does not work after re-enabling the Interactive Query toggle Key: AMBARI-16015 URL: https://issues.apache.org/jira/browse/AMBARI-16015 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.4.0 *STR* * During Install Wizard, choose HDP 2.5 * Turn on "Enable Interactive Query" from Customize Services > Hive > Config page. * When prompted, select a host for Hive Interactive * Undo "Enable Interactive Query" * Turn "Enable Interactive Query" back on * The host selection popup does not show the layout correctly (only shows Hive Interactive - it originally showed all master assignments) * Choose a different host for Hive Interactive * "HiveServer2" interactive host does not reflect the user selection (shows the original selection) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15724) Integrate Version Registration in Select Stack Page
[ https://issues.apache.org/jira/browse/AMBARI-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252077#comment-15252077 ] Hudson commented on AMBARI-15724: - FAILURE: Integrated in Ambari-trunk-Commit #4703 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4703/]) Revert "AMBARI-15724. Integrate Version Registration in Select Stack (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b842054596eb3723104eef5d5f6c8c8c7e0ee439]) * ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * ambari-web/app/controllers/installer.js * ambari-web/app/utils/db.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * ambari-web/app/views/wizard/step1_view.js * ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css * ambari-web/app/templates/wizard/step4.hbs * ambari-web/app/styles/application.less * ambari-web/app/models/stack.js * ambari-web/app/messages.js * ambari-web/test/controllers/installer_test.js * ambari-web/app/controllers/wizard/step1_controller.js * ambari-web/test/controllers/wizard/step8_test.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js * ambari-web/test/mappers/stack_mapper_test.js * ambari-web/app/views/main/admin/stack_upgrade/services_view.js * ambari-web/test/views/wizard/step1_view_test.js * ambari-web/app/mappers/stack_mapper.js * ambari-web/app/templates/wizard/step1.hbs * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * ambari-web/test/views/main/admin/stack_upgrade/services_view_test.js * ambari-web/app/controllers/wizard.js * ambari-web/app/utils/ajax/ajax.js * ambari-web/app/controllers/wizard/step8_controller.js * ambari-web/app/templates/main/admin/stack_upgrade/versions.hbs * ambari-web/app/routes/add_service_routes.js * ambari-web/app/templates/main/admin/stack_upgrade/services.hbs * ambari-web/app/mappers/repository_version_mapper.js * ambari-web/app/controllers/main/service/add_controller.js * ambari-web/app/assets/data/wizard/stack/HDP_version_definitions.json > Integrate Version Registration in Select Stack Page > --- > > Key: AMBARI-15724 > URL: https://issues.apache.org/jira/browse/AMBARI-15724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15724.patch, AMBARI-15724.patch, version1.patch, > version2.patch, version3.patch, version4.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16013:
--
Attachment: AMBARI-16013.trunk.v2.patch
AMBARI-16013.branch-2.2.v2.patch
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v2.patch,
> AMBARI-16013.trunk.v2.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16013:
--
Attachment: (was: AMBARI-16013.branch-2.2.v1.patch)
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v2.patch,
> AMBARI-16013.trunk.v2.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16013:
--
Attachment: (was: AMBARI-16013.trunk.v1.patch)
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v2.patch,
> AMBARI-16013.trunk.v2.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16007) Add sles 12 as the os family for HDP 2.5.
[ https://issues.apache.org/jira/browse/AMBARI-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252075#comment-15252075 ] Hudson commented on AMBARI-16007: - FAILURE: Integrated in Ambari-trunk-Commit #4703 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4703/]) AMBARI-16007. Add sles 12 as the os family for HDP 2.5.(vbrodetskyi) (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7799ac32fb9dc75b823069876a44f438961ba8aa]) * ambari-server/src/main/resources/stacks/HDP/2.5/repos/repoinfo.xml > Add sles 12 as the os family for HDP 2.5. > - > > Key: AMBARI-16007 > URL: https://issues.apache.org/jira/browse/AMBARI-16007 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16007.patch > > > Add sles 12 as the os family for HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15994) Restart button took about 5 minutes to appear after a config change for zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-15994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252076#comment-15252076 ] Hudson commented on AMBARI-15994: - FAILURE: Integrated in Ambari-trunk-Commit #4703 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4703/]) AMBARI-15994. Restart button took about 5 minutes to appear after a (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a242621822867b548da84b3cdcb8bad8c6dd2e50]) * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java * ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java * ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java * ambari-server/src/main/java/org/apache/ambari/server/state/Host.java > Restart button took about 5 minutes to appear after a config change for > zookeeper > - > > Key: AMBARI-15994 > URL: https://issues.apache.org/jira/browse/AMBARI-15994 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.2.2 > > Attachments: AMBARI-15994.patch > > > STR: > -Change zookeeper property "Length of single tick" from UI > This test changed the property Length of single tick from 2000 to 2001 for > Zookeeper. This should have restart indicators for Zookeeper, Storm and > Kafka. As seen from the UI, all the services had restart icons appearing late. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16005) Enhance Health Check for the Cluster before upgrading.
[
https://issues.apache.org/jira/browse/AMBARI-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252031#comment-15252031
]
Hadoop QA commented on AMBARI-16005:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799940/AMBARI-16005.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6579//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6579//console
This message is automatically generated.
> Enhance Health Check for the Cluster before upgrading.
> --
>
> Key: AMBARI-16005
> URL: https://issues.apache.org/jira/browse/AMBARI-16005
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16005.patch
>
>
> Enhance Health Check for the Cluster before upgrading.
> * check for alerts (perhaps don't start RU/EU if any blocker alerts).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15994) Restart button took about 5 minutes to appear after a config change for zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-15994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252024#comment-15252024 ] Hudson commented on AMBARI-15994: - FAILURE: Integrated in Ambari-branch-2.2 #656 (See [https://builds.apache.org/job/Ambari-branch-2.2/656/]) AMBARI-15994. Restart button took about 5 minutes to appear after a (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2bc94a04b1603aa6b2be7a9ffe7e661c01d996cf]) * ambari-server/src/main/java/org/apache/ambari/server/state/Host.java * ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java * ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java > Restart button took about 5 minutes to appear after a config change for > zookeeper > - > > Key: AMBARI-15994 > URL: https://issues.apache.org/jira/browse/AMBARI-15994 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.2.2 > > Attachments: AMBARI-15994.patch > > > STR: > -Change zookeeper property "Length of single tick" from UI > This test changed the property Length of single tick from 2000 to 2001 for > Zookeeper. This should have restart indicators for Zookeeper, Storm and > Kafka. As seen from the UI, all the services had restart icons appearing late. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16013:
--
Attachment: AMBARI-16013.trunk.v1.patch
AMBARI-16013.branch-2.2.v1.patch
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v1.patch,
> AMBARI-16013.trunk.v1.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
[
https://issues.apache.org/jira/browse/AMBARI-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-16013:
--
Status: Patch Available (was: In Progress)
> Host_status stuck in UNKNOWN status after blueprint deploy with host in
> heartbeat-lost
> --
>
> Key: AMBARI-16013
> URL: https://issues.apache.org/jira/browse/AMBARI-16013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-16013.branch-2.2.v1.patch,
> AMBARI-16013.trunk.v1.patch
>
>
> Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
> (e.g. nodes already registered with Ambari server once but than all were
> stopped prior posting the blueprint/cluster creation template to the server).
> The blueprint and cluster creation succeeded and UI looked good with all the
> hosts in heartbeat-lost state.
> Then start the agents one by one. Expected behaviour is that as soon as all
> required nodes are up Ambari to start scheduling tasks on the connected
> nodes to install the cluster.
> However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
> not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15995) ambari upgrade fail (upgrade of ambari packages ... not hdp (eu/standard) upgrade)
[ https://issues.apache.org/jira/browse/AMBARI-15995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-15995: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To https://git-wip-us.apache.org/repos/asf/ambari.git 6e46135..8416c0d trunk -> trunk > ambari upgrade fail (upgrade of ambari packages ... not hdp (eu/standard) > upgrade) > -- > > Key: AMBARI-15995 > URL: https://issues.apache.org/jira/browse/AMBARI-15995 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-15995.patch > > > Ambari packages upgrade to 2.4.0.0.160. It fails at stage of upgrading ambari > database. > Step of failure > ambari-server upgrade. > 1. It complains about following > [root@host]# ambari-server upgrade > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Can not find ambari.properties.rpmsave file from previous version, > skipping import of settings > WARNING: Can not find ambari-env.sh.rpmsave file from previous version, > skipping restore of environment settings > Fixing database objects owner > Ambari Server configured for Embedded Postgres. Confirm you have made a > backup of the Ambari Server database [y/n] (y)? y > Upgrading database schema > WARNING: Multiple versions of javax.servlet.jsp.jstl.jar found in java class > path (/usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.2.jar and > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar). > Make sure that you include only one javax.servlet.jsp.jstl.jar in the java > class path > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar'. > So I rename > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar to > something else and kept only > /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.2.jar > 2. After above changes ambari-server upgrade does finishes but throws > following error when trying to start ambari-server. > 06 Apr 2016 15:29:17,518 ERROR [main] AmbariServer:930 - Failed to run the > Ambari Server > javax.persistence.PersistenceException: Exception [EclipseLink-116] (Eclipse > Persistence Services - 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: No conversion value provided for the value [UPGRADED] > in field [host_version.state]. > Mapping: > org.eclipse.persistence.mappings.DirectToFieldMapping[state-->host_version.state] > Descriptor: > RelationalDescriptor(org.apache.ambari.server.orm.entities.HostVersionEntity > --> [DatabaseTable(host_version)]) > at > org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:484) > at org.apache.ambari.server.orm.dao.DaoUtils.selectList(DaoUtils.java:62) > at org.apache.ambari.server.orm.dao.CrudDAO.findAll(CrudDAO.java:72) > at > org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:43) > at > org.apache.ambari.server.StateRecoveryManager.checkHostAndClusterVersions(StateRecoveryManager.java:53) > at > org.apache.ambari.server.StateRecoveryManager.doWork(StateRecoveryManager.java:48) > at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:595) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:928) > Caused by: Exception [EclipseLink-116] (Eclipse Persistence Services - > 2.6.2.v20151217-774c696): > org.eclipse.persistence.exceptions.DescriptorException > Exception Description: No conversion value provided for the value [UPGRADED] > in field [host_version.state]. > Mapping: > org.eclipse.persistence.mappings.DirectToFieldMapping[state-->host_version.state] > Descriptor: > RelationalDescriptor(org.apache.ambari.server.orm.entities.HostVersionEntity > --> [DatabaseTable(host_version)]) > at > org.eclipse.persistence.exceptions.DescriptorException.noFieldValueConversionToAttributeValueProvided(DescriptorException.java:1066) > at > org.eclipse.persistence.mappings.converters.ObjectTypeConverter.convertDataValueToObjectValue(ObjectTypeConverter.java:226) > at > org.eclipse.persistence.mappings.converters.EnumTypeConverter.convertDataValueToObjectValue(EnumTypeConverter.java:141) > at > org.eclipse.persistence.mappings.foundation.AbstractDirectMapping.getObjectValue(AbstractDirectMapping.java:616) > at > org.eclipse.persistence.mappings.foundation.AbstractDirectMapping.valueFromRow(AbstractDirectMapping.java:1220) > at > org.eclipse.persistence.mappings.DatabaseMapping.readFromRowIntoObject(DatabaseMapping.java:1539) > at > org.ecl
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Status: Patch Available (was: Reopened) > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15892: --- Attachment: AMBARI-15892-2.patch > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-15892) Incorrect (Negative) values are shown for memory metrics
[ https://issues.apache.org/jira/browse/AMBARI-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened AMBARI-15892: Change should be made for another widget - Yarn Home : Cluster Memory. > Incorrect (Negative) values are shown for memory metrics > > > Key: AMBARI-15892 > URL: https://issues.apache.org/jira/browse/AMBARI-15892 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Attachments: AMBARI-15892-2.patch, AMBARI-15892.patch > > > Issue > In the "NameNode HostLoad" graph, the negative values are seen for the > computed metric "Memory Utilization" which goes by the formula : > ( mem_total - (mem_free + mem_cache) ) *100 / mem_total > Bug > AMBARI-15448 changed the way memory metrics are being reported to AMS. This > lead to a double subtraction of mem_cached, thereby leading to a negative > value intermittently. > Fix > Change the widget to : > ( mem_total - mem_free ) *100 / mem_total -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16001) Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1 upgrade
[
https://issues.apache.org/jira/browse/AMBARI-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajit Kumar updated AMBARI-16001:
Summary: Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1
upgrade (was: Fix bad entry in hbase-env.sh that were added as part of
2.2.0-2.2.1.1 upgrade)
> Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1 upgrade
> -
>
> Key: AMBARI-16001
> URL: https://issues.apache.org/jira/browse/AMBARI-16001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.2.2
>
> Attachments: rb45592.patch
>
>
> Ambari upgrades, 2.2.0-2.2.1.1 adds a bad entry to the hbase-env
> {code}export HBASE_OPTS="-Djava.io.tmpdir={{java_io_tmpdir}}"{code}
> With broken hbase-env user cannot run any mapreduce services for hbase.
> Currently it needs to be fixed manually.
> {code}
> export HBASE_OPTS="${HBASE_OPTS} -Djava.io.tmpdir={{java_io_tmpdir}}"
> {code}
> It will be good if just upgrading to 2.2.2 fixes this issue rather than
> mucking around with configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16008) Restart Phoenix Query Server intermittently fails on SLES 11 SP3
[ https://issues.apache.org/jira/browse/AMBARI-16008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-16008: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Restart Phoenix Query Server intermittently fails on SLES 11 SP3 > > > Key: AMBARI-16008 > URL: https://issues.apache.org/jira/browse/AMBARI-16008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0, 2.2.2 > > Attachments: AMBARI-16008.patch > > > Phoenix query server intermittently fails on removing the PID file for SUSE > 11sp3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16014) ambari-agent.log gets flooded up with exceptions from status commands
[
https://issues.apache.org/jira/browse/AMBARI-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-16014:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> ambari-agent.log gets flooded up with exceptions from status commands
> -
>
> Key: AMBARI-16014
> URL: https://issues.apache.org/jira/browse/AMBARI-16014
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16014.patch
>
>
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,327 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 149, in
> ApplicationTimelineServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 67, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,390 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 280, in
> Resourcemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 102, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nod
[jira] [Commented] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251948#comment-15251948 ] Andrii Tkach commented on AMBARI-16012: --- +1 for the patch > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41 > AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16011) Remove example AMS alert definitions from HDFS/alert.json
[ https://issues.apache.org/jira/browse/AMBARI-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16011: Resolution: Fixed Status: Resolved (was: Patch Available) only alerts.json changed committed to trunk > Remove example AMS alert definitions from HDFS/alert.json > - > > Key: AMBARI-16011 > URL: https://issues.apache.org/jira/browse/AMBARI-16011 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16011.patch > > > Remove example AMS alert definitions from HDFS alert.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-16012: --- Attachment: AMBARI-16012.patch > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41 > AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16014) ambari-agent.log gets flooded up with exceptions from status commands
[
https://issues.apache.org/jira/browse/AMBARI-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-16014:
-
Attachment: AMBARI-16014.patch
> ambari-agent.log gets flooded up with exceptions from status commands
> -
>
> Key: AMBARI-16014
> URL: https://issues.apache.org/jira/browse/AMBARI-16014
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16014.patch
>
>
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,327 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 149, in
> ApplicationTimelineServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 67, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,390 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 280, in
> Resourcemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 102, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/
[jira] [Created] (AMBARI-16014) ambari-agent.log gets flooded up with exceptions from status commands
Andrew Onischuk created AMBARI-16014:
Summary: ambari-agent.log gets flooded up with exceptions from
status commands
Key: AMBARI-16014
URL: https://issues.apache.org/jira/browse/AMBARI-16014
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.4.0
Attachments: AMBARI-16014.patch
is_linux_container_executor =
(yarn_nodemanager_container_executor_class ==
'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found
in configurations dictionary!")
Fail: Configuration parameter 'yarn-site' was not found in configurations
dictionary!
INFO 2016-04-21 12:14:21,327 PythonReflectiveExecutor.py:65 - Reflective
command failed with exception:
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
line 57, in run_file
imp.load_source('__main__', script)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
line 149, in
ApplicationTimelineServer().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 251, in execute
self.save_component_version_to_structured_out()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 166, in save_component_version_to_structured_out
component_name = self.get_component_name()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 152, in get_component_name
stack_to_component = self.get_stack_to_component()
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
line 67, in get_stack_to_component
import params
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
line 28, in
from params_linux import *
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
line 144, in
is_linux_container_executor =
(yarn_nodemanager_container_executor_class ==
'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found
in configurations dictionary!")
Fail: Configuration parameter 'yarn-site' was not found in configurations
dictionary!
INFO 2016-04-21 12:14:21,390 PythonReflectiveExecutor.py:65 - Reflective
command failed with exception:
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
line 57, in run_file
imp.load_source('__main__', script)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
line 280, in
Resourcemanager().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 251, in execute
self.save_component_version_to_structured_out()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 166, in save_component_version_to_structured_out
component_name = self.get_component_name()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 152, in get_component_name
stack_to_component = self.get_stack_to_component()
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
line 102, in get_stack_to_component
import params
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
line 28, in
from params_linux import *
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
line 144, in
is_linux_container_executor =
(yarn_nodemanager_container_executor_class ==
'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found
in configurations dictionary!")
Fail: Configuration parameter 'yarn-site' was not found in configurations
dictionary!
INFO 2016-04-21 12:14:21,429 PythonReflectiveExecutor.py:65 - Reflective
command failed with
[jira] [Commented] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251941#comment-15251941 ] Oleg Nechiporenko commented on AMBARI-16012: 27527 tests complete (43 seconds) 154 tests pending > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41 > AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-16012: --- Status: Patch Available (was: Open) Patch added > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41 > AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16014) ambari-agent.log gets flooded up with exceptions from status commands
[
https://issues.apache.org/jira/browse/AMBARI-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-16014:
-
Status: Patch Available (was: Open)
> ambari-agent.log gets flooded up with exceptions from status commands
> -
>
> Key: AMBARI-16014
> URL: https://issues.apache.org/jira/browse/AMBARI-16014
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16014.patch
>
>
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,327 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 149, in
> ApplicationTimelineServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
> line 67, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> Fail: Configuration parameter 'yarn-site' was not found in configurations
> dictionary!
> INFO 2016-04-21 12:14:21,390 PythonReflectiveExecutor.py:65 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 57, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 280, in
> Resourcemanager().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 251, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 166, in save_component_version_to_structured_out
> component_name = self.get_component_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 152, in get_component_name
> stack_to_component = self.get_stack_to_component()
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py",
> line 102, in get_stack_to_component
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py",
> line 28, in
> from params_linux import *
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py",
> line 144, in
> is_linux_container_executor =
> (yarn_nodemanager_container_executor_class ==
> 'org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor')
> File
>
[jira] [Created] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
Sebastian Toader created AMBARI-16013:
-
Summary: Host_status stuck in UNKNOWN status after blueprint
deploy with host in heartbeat-lost
Key: AMBARI-16013
URL: https://issues.apache.org/jira/browse/AMBARI-16013
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Sebastian Toader
Assignee: Sebastian Toader
Priority: Blocker
Fix For: 2.2.2
Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state
(e.g. nodes already registered with Ambari server once but than all were
stopped prior posting the blueprint/cluster creation template to the server).
The blueprint and cluster creation succeeded and UI looked good with all the
hosts in heartbeat-lost state.
Then start the agents one by one. Expected behaviour is that as soon as all
required nodes are up Ambari to start scheduling tasks on the connected nodes
to install the cluster.
However the hosts were stuck in {{host_status: UNKNOWN}} state and Ambari did
not start scheduling any tasks to the connected hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-16012: --- Attachment: Screen Shot 2016-04-20 at 11.16.52 AM.png Screen Shot 2016-04-20 at 11.16.41 AM.png > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-04-20 at 11.16.41 AM.png, Screen Shot > 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16006) Add logging to check_host.py
[ https://issues.apache.org/jira/browse/AMBARI-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16006: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Add logging to check_host.py > > > Key: AMBARI-16006 > URL: https://issues.apache.org/jira/browse/AMBARI-16006 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16006.patch > > > Sometimes host check after host registration lasted too long (more than 720 > sec.). I's affect some system tests. I can't reproduce this, so it would be > good to add logging to this operation. > Currently, all the host check logs available are > > > > [root@c6404 data]# cat /var/lib/ambari-agent/data/output-3.txt > Last Agent Env check started. > Last Agent Env check completed successfully. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16012) JS error logged in dev console on signing in to ambari
Oleg Nechiporenko created AMBARI-16012: -- Summary: JS error logged in dev console on signing in to ambari Key: AMBARI-16012 URL: https://issues.apache.org/jira/browse/AMBARI-16012 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 2.4.0 *STR:* # Deploy a cluster with HDFS and YARN # Log off from ambari # Refresh browser # Log in to Ambari JS error as shown in attachment is generated. This issue happens intermittently with the stated STR as this seems to be timing issue. It seems that multiple quick links widgets on dashboard page are calling [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] and this generates error at [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] I haven't verified but this issue might affect http/https formation in quick link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16011) Remove example AMS alert definitions from HDFS/alert.json
[ https://issues.apache.org/jira/browse/AMBARI-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16011: Attachment: AMBARI-16011.patch > Remove example AMS alert definitions from HDFS/alert.json > - > > Key: AMBARI-16011 > URL: https://issues.apache.org/jira/browse/AMBARI-16011 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16011.patch > > > Remove example AMS alert definitions from HDFS alert.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16011) Remove example AMS alert definitions from HDFS/alert.json
[ https://issues.apache.org/jira/browse/AMBARI-16011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16011: Status: Patch Available (was: Open) > Remove example AMS alert definitions from HDFS/alert.json > - > > Key: AMBARI-16011 > URL: https://issues.apache.org/jira/browse/AMBARI-16011 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16011.patch > > > Remove example AMS alert definitions from HDFS alert.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15752) Ambari support for additional config params for Ranger KMS to support HSM
[ https://issues.apache.org/jira/browse/AMBARI-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-15752: -- Fix Version/s: 2.4.0 > Ambari support for additional config params for Ranger KMS to support HSM > - > > Key: AMBARI-15752 > URL: https://issues.apache.org/jira/browse/AMBARI-15752 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0, ambari-2.4.0 > > Attachments: AMBARI-15752.1.patch, AMBARI-15752.2.patch, > AMBARI-15752.3.patch, AMBARI-15752.patch > > > Add HSM support configuration properties for Ranger KMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16011) Remove example AMS alert definitions from HDFS/alert.json
Dmytro Sen created AMBARI-16011: --- Summary: Remove example AMS alert definitions from HDFS/alert.json Key: AMBARI-16011 URL: https://issues.apache.org/jira/browse/AMBARI-16011 Project: Ambari Issue Type: Bug Components: alerts Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.4.0 Remove example AMS alert definitions from HDFS alert.json -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15752) Ambari support for additional config params for Ranger KMS to support HSM
[ https://issues.apache.org/jira/browse/AMBARI-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251927#comment-15251927 ] Gautam Borad commented on AMBARI-15752: --- Committed to trunk : https://github.com/apache/ambari/commit/8006d3d6a77615b43aeb619bac6231d9f3ff2b75 > Ambari support for additional config params for Ranger KMS to support HSM > - > > Key: AMBARI-15752 > URL: https://issues.apache.org/jira/browse/AMBARI-15752 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-15752.1.patch, AMBARI-15752.2.patch, > AMBARI-15752.3.patch, AMBARI-15752.patch > > > Add HSM support configuration properties for Ranger KMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15752) Ambari support for additional config params for Ranger KMS to support HSM
[ https://issues.apache.org/jira/browse/AMBARI-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated AMBARI-15752: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari support for additional config params for Ranger KMS to support HSM > - > > Key: AMBARI-15752 > URL: https://issues.apache.org/jira/browse/AMBARI-15752 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-15752.1.patch, AMBARI-15752.2.patch, > AMBARI-15752.3.patch, AMBARI-15752.patch > > > Add HSM support configuration properties for Ranger KMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15792) HIVE service_check doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-15792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251914#comment-15251914 ] Hudson commented on AMBARI-15792: - SUCCESS: Integrated in Ambari-trunk-Commit #4702 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4702/]) AMBARI-15792. AMBARI-15792: HIVE service_check doesn't work properly (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8a6141a46808ac28a04dbcd5ee4b9d204b4eea38]) * ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service_check.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/files/templetonSmoke.sh > HIVE service_check doesn't work properly > > > Key: AMBARI-15792 > URL: https://issues.apache.org/jira/browse/AMBARI-15792 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.1 > Environment: HDP2.4 >Reporter: Masahiro TANAKA >Assignee: Andrew Onischuk > Labels: patch-available > Fix For: 2.4.0 > > Attachments: AMBARI-15792.patch, AMBARI-15792.v2.patch, > AMBARI-15792.v3.patch, AMBARI-15792.v4.patch > > > In templetonSmoke.sh, there are > 1) unnecessary `exit 0` > 2) lack of redirect `>` command > 3) unassigned variable > we should correct them all to check the HIVE service properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15915) SQL constraints: Inline constraints and name them in CREATE table
[
https://issues.apache.org/jira/browse/AMBARI-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251921#comment-15251921
]
Sebastian Toader commented on AMBARI-15915:
---
{code}
commit 346dfe7eb78b8a71e4981c034fb2f3fddba0db81
Author: Balazs Bence Sari
Date: Thu Apr 21 13:18:58 2016 +0200
AMBARI-15915. SQL constraints: Inline constraints and name them in CREATE
table. (Balazs Bence Sari via stoader)
{code}
> SQL constraints: Inline constraints and name them in CREATE table
> -
>
> Key: AMBARI-15915
> URL: https://issues.apache.org/jira/browse/AMBARI-15915
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sebastian Toader
>Assignee: Balázs Bence Sári
> Fix For: 2.4.0
>
> Attachments: patch2.diff
>
>
> Move ALTER TABLE statements for unique and foreign key constraints into the
> CREATE table statement.
> Also provide primary key constraint names where primary keys are specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
