[jira] [Resolved] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar resolved AMBARI-21963.
--
Resolution: Fixed
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21963.patch
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167316#comment-16167316
]
Swapan Shridhar commented on AMBARI-21963:
--
Committed to branch : branch-feature-AMBARI-14714
{code}
commit 12bf5e46372d0fa91bf86c0581ad82f15b54740b
Author: Swapan Shridhar
Date: Thu Sep 14 20:51:57 2017 -0700
AMBARI-21963. Ambari-server gives database consistency error : ERROR:
column hcs.service_name does not exist.
{code}
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21963.patch
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167293#comment-16167293
]
Madhuvanthi Radhakrishnan commented on AMBARI-21963:
+1 LGTM
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21963.patch
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167289#comment-16167289
]
Swapan Shridhar commented on AMBARI-21963:
--
[^AMBARI-21963.patch] for review. [~jluniya] | [~mradhakrishnan]
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21963.patch
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21963:
-
Attachment: AMBARI-21963.patch
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21963.patch
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
[
https://issues.apache.org/jira/browse/AMBARI-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21963:
-
Description:
In DatabaseConsistencyCheckerHelper : There is a query that is executed to
verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
{code}
String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM hostcomponentstate
hcs " +
"JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name AND
hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
{code}
With service group changes, *hostcomponentstate* and
*hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
added a column for *service_group_id*.
*Fix:* Use *service_id* and *service_group_id* in query.
> Ambari-server gives database consistency error : ERROR: column
> hcs.service_name does not exis
> -
>
> Key: AMBARI-21963
> URL: https://issues.apache.org/jira/browse/AMBARI-21963
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
>
> In DatabaseConsistencyCheckerHelper : There is a query that is executed to
> verify count of rows in *hostcomponentstate* and *hostcomponentdesiredstate*.
> {code}
> String GET_MERGED_TABLE_ROW_COUNT_QUERY = "select count FROM
> hostcomponentstate hcs " +
> "JOIN hostcomponentdesiredstate hcds ON hcs.service_name=hcds.service_name
> AND hcs.component_name=hcds.component_name AND hcs.host_id=hcds.host_id";
> {code}
> With service group changes, *hostcomponentstate* and
> *hostcomponentdesiredstate* has replaced *service_name* with *service_id* and
> added a column for *service_group_id*.
> *Fix:* Use *service_id* and *service_group_id* in query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21963) Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis
Swapan Shridhar created AMBARI-21963: Summary: Ambari-server gives database consistency error : ERROR: column hcs.service_name does not exis Key: AMBARI-21963 URL: https://issues.apache.org/jira/browse/AMBARI-21963 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.1 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Priority: Blocker Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167253#comment-16167253
]
zhangxiaolu commented on AMBARI-20437:
--
Hi [~dsen] and [~nc...@hortonworks.com] Thank you so much for reviewing my
patch on reviewboard, and could you be so kind as to commit the patch for me
please? Thanks in advance
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21856) Service repoinfo.xml needs to expose component for Ubuntu repos
[ https://issues.apache.org/jira/browse/AMBARI-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21856: --- Attachment: AMBARI-21856.patch > Service repoinfo.xml needs to expose component for Ubuntu repos > --- > > Key: AMBARI-21856 > URL: https://issues.apache.org/jira/browse/AMBARI-21856 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.6.0 > > Attachments: AMBARI-21856.patch > > > The problem is that Ambari is using the reponame name field as the > distribution when it creates the repo definition file. Since both of these > repos use same distribution (which is a common Debian pattern), they collide. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21856) Service repoinfo.xml needs to expose component for Ubuntu repos
[ https://issues.apache.org/jira/browse/AMBARI-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21856: --- Attachment: (was: AMBARI-21856.patch) > Service repoinfo.xml needs to expose component for Ubuntu repos > --- > > Key: AMBARI-21856 > URL: https://issues.apache.org/jira/browse/AMBARI-21856 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.6.0 > > Attachments: AMBARI-21856.patch > > > The problem is that Ambari is using the reponame name field as the > distribution when it creates the repo definition file. Since both of these > repos use same distribution (which is a common Debian pattern), they collide. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21962) Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either
[ https://issues.apache.org/jira/browse/AMBARI-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21962: - Status: Patch Available (was: Open) > Components Filter has a preselected component from a deleted conf group while > adding hosts to a new conf group. Hosts listed are not correct either > --- > > Key: AMBARI-21962 > URL: https://issues.apache.org/jira/browse/AMBARI-21962 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21962_branch-2.6.patch, AMBARI-21962.patch > > > Create a new config group > Add only NN host to be a member of this group > Update a property and save to this conf group. > Delete this conf group > Now go to Manage config group again to create a new group. While adding hosts > to this config group, click on Components filter to choose a component > (Namenode in this case). Looks like Namenode is already selected (actual.png) > which is not right. Expected to be as in expected.png > Even if namenode is selected the hosts shown on the popup window contains all > nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21962) Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either
[ https://issues.apache.org/jira/browse/AMBARI-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21962: - Attachment: AMBARI-21962.patch > Components Filter has a preselected component from a deleted conf group while > adding hosts to a new conf group. Hosts listed are not correct either > --- > > Key: AMBARI-21962 > URL: https://issues.apache.org/jira/browse/AMBARI-21962 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21962_branch-2.6.patch, AMBARI-21962.patch > > > Create a new config group > Add only NN host to be a member of this group > Update a property and save to this conf group. > Delete this conf group > Now go to Manage config group again to create a new group. While adding hosts > to this config group, click on Components filter to choose a component > (Namenode in this case). Looks like Namenode is already selected (actual.png) > which is not right. Expected to be as in expected.png > Even if namenode is selected the hosts shown on the popup window contains all > nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21962) Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either
[ https://issues.apache.org/jira/browse/AMBARI-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21962: - Attachment: (was: AMBARI-21962.patch) > Components Filter has a preselected component from a deleted conf group while > adding hosts to a new conf group. Hosts listed are not correct either > --- > > Key: AMBARI-21962 > URL: https://issues.apache.org/jira/browse/AMBARI-21962 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21962_branch-2.6.patch > > > Create a new config group > Add only NN host to be a member of this group > Update a property and save to this conf group. > Delete this conf group > Now go to Manage config group again to create a new group. While adding hosts > to this config group, click on Components filter to choose a component > (Namenode in this case). Looks like Namenode is already selected (actual.png) > which is not right. Expected to be as in expected.png > Even if namenode is selected the hosts shown on the popup window contains all > nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21962) Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either
[ https://issues.apache.org/jira/browse/AMBARI-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21962: - Attachment: AMBARI-21962.patch AMBARI-21962_branch-2.6.patch > Components Filter has a preselected component from a deleted conf group while > adding hosts to a new conf group. Hosts listed are not correct either > --- > > Key: AMBARI-21962 > URL: https://issues.apache.org/jira/browse/AMBARI-21962 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21962_branch-2.6.patch, AMBARI-21962.patch > > > Create a new config group > Add only NN host to be a member of this group > Update a property and save to this conf group. > Delete this conf group > Now go to Manage config group again to create a new group. While adding hosts > to this config group, click on Components filter to choose a component > (Namenode in this case). Looks like Namenode is already selected (actual.png) > which is not right. Expected to be as in expected.png > Even if namenode is selected the hosts shown on the popup window contains all > nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21962) Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either
Ishan Bhatt created AMBARI-21962: Summary: Components Filter has a preselected component from a deleted conf group while adding hosts to a new conf group. Hosts listed are not correct either Key: AMBARI-21962 URL: https://issues.apache.org/jira/browse/AMBARI-21962 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk, 2.6.0 Create a new config group Add only NN host to be a member of this group Update a property and save to this conf group. Delete this conf group Now go to Manage config group again to create a new group. While adding hosts to this config group, click on Components filter to choose a component (Namenode in this case). Looks like Namenode is already selected (actual.png) which is not right. Expected to be as in expected.png Even if namenode is selected the hosts shown on the popup window contains all nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21951) Last Run Service Check for SPARK Picks up SPARK2
[
https://issues.apache.org/jira/browse/AMBARI-21951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166953#comment-16166953
]
Hudson commented on AMBARI-21951:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #215 (See
[https://builds.apache.org/job/Ambari-branch-2.6/215/])
AMBARI-21951 - Last Run Service Check for SPARK Picks up SPARK2 (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=93da018778931046fdcc30221d40c18bcfe66a1b])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostRoleCommandEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServiceCheckValidityCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/ServiceCheckValidityCheck.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java
> Last Run Service Check for SPARK Picks up SPARK2
>
>
> Key: AMBARI-21951
> URL: https://issues.apache.org/jira/browse/AMBARI-21951
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21951.patch
>
>
> STR:
> - Install a cluster with Spark and Spark2
> - Remove Spark2
> - Change a Spark configuration
> - Run the Spark Service check
> - Attempt to perform an upgrade
> The upgrade pre-checks will stop you saying something like:
> {code}
> 02 Aug 2017 10:17:23,701 INFO [ambari-client-thread-28]
> ServiceCheckValidityCheck:149 - Service SPARK latest config change is
> 08-02-2017 09:45:16, latest service check executed at 12-31-1969 03:59:59
> {code}
> The start time suggests a value of -1 in my cluster. The problem is that I
> aborted my SPARK2 service check and then removed the service. However, the
> pre-check seems to be matching on the name an incorrectly detecting the old
> SPARK2 check as the one for SPARK:
> {code}
> boolean serviceCheckWasExecuted = false;
> for (HostRoleCommandEntity command : latestTimestamps.values()) {
> if (null != command.getCommandDetail() &&
> command.getCommandDetail().contains(serviceName)) {
> {code}
> Because {{contains()}} is finding {{SPARK}} in {{SPARK2_SERVICE_CHECK}}, it's
> incorrectly picking up the wrong values...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166954#comment-16166954 ] Hudson commented on AMBARI-21961: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #215 (See [https://builds.apache.org/job/Ambari-branch-2.6/215/]) AMBARI-21961. UI showing confirmation when no services will be installed (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1694faa547171811fe04fc539069e85821c2787c]) * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21961.patch > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21951) Last Run Service Check for SPARK Picks up SPARK2
[
https://issues.apache.org/jira/browse/AMBARI-21951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166947#comment-16166947
]
Hudson commented on AMBARI-21951:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8065 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8065/])
AMBARI-21951 - Last Run Service Check for SPARK Picks up SPARK2 (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6cee80b1894276608e53f3b0f4711acf23b1a975])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostRoleCommandEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServiceCheckValidityCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/ServiceCheckValidityCheck.java
> Last Run Service Check for SPARK Picks up SPARK2
>
>
> Key: AMBARI-21951
> URL: https://issues.apache.org/jira/browse/AMBARI-21951
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21951.patch
>
>
> STR:
> - Install a cluster with Spark and Spark2
> - Remove Spark2
> - Change a Spark configuration
> - Run the Spark Service check
> - Attempt to perform an upgrade
> The upgrade pre-checks will stop you saying something like:
> {code}
> 02 Aug 2017 10:17:23,701 INFO [ambari-client-thread-28]
> ServiceCheckValidityCheck:149 - Service SPARK latest config change is
> 08-02-2017 09:45:16, latest service check executed at 12-31-1969 03:59:59
> {code}
> The start time suggests a value of -1 in my cluster. The problem is that I
> aborted my SPARK2 service check and then removed the service. However, the
> pre-check seems to be matching on the name an incorrectly detecting the old
> SPARK2 check as the one for SPARK:
> {code}
> boolean serviceCheckWasExecuted = false;
> for (HostRoleCommandEntity command : latestTimestamps.values()) {
> if (null != command.getCommandDetail() &&
> command.getCommandDetail().contains(serviceName)) {
> {code}
> Because {{contains()}} is finding {{SPARK}} in {{SPARK2_SERVICE_CHECK}}, it's
> incorrectly picking up the wrong values...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166948#comment-16166948 ] Hudson commented on AMBARI-21961: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8065 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8065/]) AMBARI-21961. UI showing confirmation when no services will be installed (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54435dbb29f4e07a16cc9c032c444c7028461986]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21961.patch > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166885#comment-16166885 ] Hudson commented on AMBARI-21957: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #214 (See [https://builds.apache.org/job/Ambari-branch-2.6/214/]) AMBARI-21957. UI should handle rejection of PATCH VDF (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d277acbd87179d8721e3da5e50867fea11c2c4a]) * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21957.patch > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166881#comment-16166881 ] Hudson commented on AMBARI-21957: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8064 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8064/]) AMBARI-21957. UI should handle rejection of PATCH VDF (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=95d6ff0b03582b0c4132ee8575d8f688e033c9ee]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21957.patch > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21961: - Resolution: Fixed Status: Resolved (was: Patch Available) Jenkins doesn't run jobs. Manually tested. Committed to trunk and branch-2.6 > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21961.patch > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21951) Last Run Service Check for SPARK Picks up SPARK2
[
https://issues.apache.org/jira/browse/AMBARI-21951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21951:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Last Run Service Check for SPARK Picks up SPARK2
>
>
> Key: AMBARI-21951
> URL: https://issues.apache.org/jira/browse/AMBARI-21951
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21951.patch
>
>
> STR:
> - Install a cluster with Spark and Spark2
> - Remove Spark2
> - Change a Spark configuration
> - Run the Spark Service check
> - Attempt to perform an upgrade
> The upgrade pre-checks will stop you saying something like:
> {code}
> 02 Aug 2017 10:17:23,701 INFO [ambari-client-thread-28]
> ServiceCheckValidityCheck:149 - Service SPARK latest config change is
> 08-02-2017 09:45:16, latest service check executed at 12-31-1969 03:59:59
> {code}
> The start time suggests a value of -1 in my cluster. The problem is that I
> aborted my SPARK2 service check and then removed the service. However, the
> pre-check seems to be matching on the name an incorrectly detecting the old
> SPARK2 check as the one for SPARK:
> {code}
> boolean serviceCheckWasExecuted = false;
> for (HostRoleCommandEntity command : latestTimestamps.values()) {
> if (null != command.getCommandDetail() &&
> command.getCommandDetail().contains(serviceName)) {
> {code}
> Because {{contains()}} is finding {{SPARK}} in {{SPARK2_SERVICE_CHECK}}, it's
> incorrectly picking up the wrong values...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21961: - Attachment: AMBARI-21961.patch > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21961.patch > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21961: - Status: Patch Available (was: Open) > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21961.patch > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21961) UI showing confirmation when no services will be installed
[ https://issues.apache.org/jira/browse/AMBARI-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21961: Assignee: Antonenko Alexander > UI showing confirmation when no services will be installed > -- > > Key: AMBARI-21961 > URL: https://issues.apache.org/jira/browse/AMBARI-21961 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > > STR: > 1. Install a ZK or ZK+Storm cluster > 2. Register a VDF that contains only Atlas (Atlas is not installed) > 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21961) UI showing confirmation when no services will be installed
Antonenko Alexander created AMBARI-21961: Summary: UI showing confirmation when no services will be installed Key: AMBARI-21961 URL: https://issues.apache.org/jira/browse/AMBARI-21961 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 STR: 1. Install a ZK or ZK+Storm cluster 2. Register a VDF that contains only Atlas (Atlas is not installed) 3. UI shows a confirm dialog with an empty service list (see screenshot -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21957: - Resolution: Fixed Status: Resolved (was: Patch Available) Build fails on ambari-server. Manually tested. Committed to trunk and branch-2.6 > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21957.patch > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21957) UI should handle rejection of PATCH VDF
[
https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166836#comment-16166836
]
Hadoop QA commented on AMBARI-21957:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887091/AMBARI-21957.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12226//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12226//console
This message is automatically generated.
> UI should handle rejection of PATCH VDF
> ---
>
> Key: AMBARI-21957
> URL: https://issues.apache.org/jira/browse/AMBARI-21957
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21957.patch
>
>
> As of now, UI just breaks when VDF is rejected
> STR
> # Install ZooKeeper, HDFS on HDP 2.6.0.1-207
> # Register the attached VDF
> # Try to start upgrade
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166785#comment-16166785 ] Hudson commented on AMBARI-21960: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8063 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8063/]) AMBARI-21960. Cluster provision should allow repo version and repo (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3affda38defa4f74ae981e78b6c85c0048635fb2]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id null checks for BP > deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166740#comment-16166740
]
Hadoop QA commented on AMBARI-21959:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887105/AMBARI-21959.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12225//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12225//console
This message is automatically generated.
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21959_branch-2.6.patch, AMBARI-21959.patch
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21953) Move Masters and Host Recovery fixes
[ https://issues.apache.org/jira/browse/AMBARI-21953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21953: - Fix Version/s: trunk > Move Masters and Host Recovery fixes > > > Key: AMBARI-21953 > URL: https://issues.apache.org/jira/browse/AMBARI-21953 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21953_branch-2.6patch, AMBARI-21953.patch > > > UI fixes for host recovery and move master wizard -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21953) Move Masters and Host Recovery fixes
[ https://issues.apache.org/jira/browse/AMBARI-21953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21953: - Status: Open (was: Patch Available) > Move Masters and Host Recovery fixes > > > Key: AMBARI-21953 > URL: https://issues.apache.org/jira/browse/AMBARI-21953 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21953_branch-2.6patch, AMBARI-21953.patch > > > UI fixes for host recovery and move master wizard -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21953) Move Masters and Host Recovery fixes
[ https://issues.apache.org/jira/browse/AMBARI-21953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21953: - Status: Patch Available (was: Open) > Move Masters and Host Recovery fixes > > > Key: AMBARI-21953 > URL: https://issues.apache.org/jira/browse/AMBARI-21953 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21953_branch-2.6patch, AMBARI-21953.patch > > > UI fixes for host recovery and move master wizard -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21953) Move Masters and Host Recovery fixes
[ https://issues.apache.org/jira/browse/AMBARI-21953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21953: - Fix Version/s: 2.6.0 > Move Masters and Host Recovery fixes > > > Key: AMBARI-21953 > URL: https://issues.apache.org/jira/browse/AMBARI-21953 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21953_branch-2.6patch, AMBARI-21953.patch > > > UI fixes for host recovery and move master wizard -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[
https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166729#comment-16166729
]
Hadoop QA commented on AMBARI-21885:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887137/AMBARI-21885.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12224//console
This message is automatically generated.
> Config group filter in Dashboard page shows 'All' even if you choose a config
> group
> ---
>
> Key: AMBARI-21885
> URL: https://issues.apache.org/jira/browse/AMBARI-21885
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Dhanya Balasundaran
>Assignee: Andrii Tkach
> Fix For: 2.6.0
>
> Attachments: AMBARI-21885.patch
>
>
> - Naviagte to Config History tab in dashboard page.
> - From the dropdown for config groups select a conf group name. Even though
> the config group is selected fine, UI shows All
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21953) Move Masters and Host Recovery fixes
[
https://issues.apache.org/jira/browse/AMBARI-21953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166726#comment-16166726
]
Hadoop QA commented on AMBARI-21953:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12886989/AMBARI-21953.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12223//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12223//console
This message is automatically generated.
> Move Masters and Host Recovery fixes
>
>
> Key: AMBARI-21953
> URL: https://issues.apache.org/jira/browse/AMBARI-21953
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Attachments: AMBARI-21953_branch-2.6patch, AMBARI-21953.patch
>
>
> UI fixes for host recovery and move master wizard
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21955) Port Storm View from React.js to Vue.js
[
https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166716#comment-16166716
]
Hadoop QA commented on AMBARI-21955:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887046/AMBARI-21955.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/1//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1//console
This message is automatically generated.
> Port Storm View from React.js to Vue.js
> ---
>
> Key: AMBARI-21955
> URL: https://issues.apache.org/jira/browse/AMBARI-21955
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.6.0
>Reporter: Sanket Shah
>Assignee: Sanket Shah
> Attachments: AMBARI-21955.patch
>
>
> The Apache Software Foundation Legal Affairs Committee [has announced |
> https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that
> the so-called 'Facebook BSD+Patents License' is no longer allowed to be used
> as a direct dependency in Apache projects.
> Since Storm View is using React.js which is under the same Facebook's
> license, needs to get rid of and use Vue.js instead.
> cc: [~ggolani]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21958) Fix broken zeppelin python unit test
[ https://issues.apache.org/jira/browse/AMBARI-21958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166710#comment-16166710 ] Hudson commented on AMBARI-21958: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8062 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8062/]) AMBARI-21958 - Fix broken zeppelin python unit test (Prabhjyot Singh via (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6b19bc46f7c2b8cb7bd8803c213fc3b13fde6418]) * (add) ambari-server/src/test/python/stacks/2.5/ZEPPELIN/interpreter_json_generated.py * (edit) ambari-server/src/test/python/stacks/2.5/configs/secured.json * (edit) ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py * (edit) ambari-server/src/test/python/stacks/2.5/configs/default.json > Fix broken zeppelin python unit test > > > Key: AMBARI-21958 > URL: https://issues.apache.org/jira/browse/AMBARI-21958 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0 > > Attachments: AMBARI-21958_trunk_v1.patch, AMBARI-21958_trunk_v2.patch > > > test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be > happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21957) UI should handle rejection of PATCH VDF
[
https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166697#comment-16166697
]
Hadoop QA commented on AMBARI-21957:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887091/AMBARI-21957.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12221//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12221//console
This message is automatically generated.
> UI should handle rejection of PATCH VDF
> ---
>
> Key: AMBARI-21957
> URL: https://issues.apache.org/jira/browse/AMBARI-21957
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21957.patch
>
>
> As of now, UI just breaks when VDF is rejected
> STR
> # Install ZooKeeper, HDFS on HDP 2.6.0.1-207
> # Register the attached VDF
> # Try to start upgrade
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166692#comment-16166692 ] Hudson commented on AMBARI-21960: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #213 (See [https://builds.apache.org/job/Ambari-branch-2.6/213/]) AMBARI-21960. Cluster provision should allow repo version and repo (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bf3a485e4b9f2eace27dc2a088f5d120285bb845]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id null checks for BP > deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166674#comment-16166674
]
Hadoop QA commented on AMBARI-21959:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887105/AMBARI-21959.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12220//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12220//console
This message is automatically generated.
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21959_branch-2.6.patch, AMBARI-21959.patch
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21945) Refresh Include/Exclude breaks parallel operations and can't be turned off
[
https://issues.apache.org/jira/browse/AMBARI-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1614#comment-1614
]
Hadoop QA commented on AMBARI-21945:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887126/AMBARI-21945_2.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12219//console
This message is automatically generated.
> Refresh Include/Exclude breaks parallel operations and can't be turned off
> --
>
> Key: AMBARI-21945
> URL: https://issues.apache.org/jira/browse/AMBARI-21945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.6.0
>
> Attachments: AMBARI-21945_2.patch, AMBARI-21945.patch
>
>
> Each time a new server is registered, there is an operation to refresh HDFS
> and YARN exclude file and now the operations (install components + start
> components) in Ambari can not be executed in parallel b/c refresh exclude
> file is an atomic process. Each server's operations of install and start
> components processes have to await previous one's refresh node to be
> finished. This means adding servers through blueprint is extremely slow now
> when many servers are being launched at the similar time.
> Also the refresh exclude file for each servers are still being executed even
> when 'manage.include.files' flags are turned off in yarn-site and hdfs-site.
> Previously in 2.5.1 we mange refresh files after adding / removing each batch
> of the servers, now seems this is impossible in 2.5.2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21960: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id null checks for BP > deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21885: -- Fix Version/s: 2.6.0 > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21885.patch > > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166624#comment-16166624 ] Aleksandr Kovalenko commented on AMBARI-21885: -- +1 for the patch > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21885.patch > > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21950) Package Installation is failing If Patch-VDF contain service that is not installed in the cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166617#comment-16166617 ] Hudson commented on AMBARI-21950: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8061 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8061/]) AMBARI-21950. Package Installation is failing If Patch-VDF contain (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1f6b9daf2f7e559705c00d2ac8428af1337f5e4d]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java > Package Installation is failing If Patch-VDF contain service that is not > installed in the cluster. > -- > > Key: AMBARI-21950 > URL: https://issues.apache.org/jira/browse/AMBARI-21950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21950.patch > > > The BE is checking for services in the cluster after it marks hosts as > INSTALLING -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21948) Final flag is available for a property which is 'Undefined' in Default config group
[ https://issues.apache.org/jira/browse/AMBARI-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166615#comment-16166615 ] Hudson commented on AMBARI-21948: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8061 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8061/]) AMBARI-21948. Final flag is available for a property which is (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=03edb8e780f12c83ba918b9bc2b1b4cf06057ea6]) * (edit) ambari-web/app/views/common/configs/controls_view.js > Final flag is available for a property which is 'Undefined' in Default config > group > --- > > Key: AMBARI-21948 > URL: https://issues.apache.org/jira/browse/AMBARI-21948 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21948_branch-2.6.patch, AMBARI-21948.patch > > > When you switch to new config group, it shows the current value of property > in Default config group which is 'Undefined', but it has a 'Final' flag > option available too. > Doesn't look like its expected because even if you try to set the flag for > 'Undefined' Save button is not enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21933) Implement breadcrumbs in Background Operations modal
[ https://issues.apache.org/jira/browse/AMBARI-21933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166616#comment-16166616 ] Hudson commented on AMBARI-21933: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8061 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8061/]) AMBARI-21933 - UI: Implement breadcrumbs in Background Operations modal (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38604db2f17eb7eac3b4fe5bf308842d5018ee00]) * (edit) ambari-web/app/templates/common/host_progress_popup.hbs * (edit) ambari-web/app/templates/common/breadcrumbs.hbs * (edit) ambari-web/test/views/common/breadcrumbs_view_test.js * (edit) ambari-web/app/views/common/host_progress_popup_body_view.js * (edit) ambari-web/app/controllers/global/background_operations_controller.js * (edit) ambari-web/test/controllers/global/background_operations_test.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/progress_popup_controller.js * (edit) ambari-web/app/styles/modal_popups.less * (edit) ambari-web/test/utils/host_progress_popup_test.js * (edit) ambari-web/app/utils/host_progress_popup.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/progress_popup_controller_test.js * (edit) ambari-web/test/views/common/host_progress_popup_body_view_test.js * (edit) ambari-web/app/views/common/breadcrumbs_view.js * (edit) ambari-web/app/messages.js > Implement breadcrumbs in Background Operations modal > > > Key: AMBARI-21933 > URL: https://issues.apache.org/jira/browse/AMBARI-21933 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb > Fix For: 3.0.0 > > Attachments: AMBARI-21933.patch > > > Implement breadcrumb navigation in the Background Operations modal and the > drill-down views within it. This also affects the use of these views in the > High Availability wizard. The breadcrumbs will provide a better navigation > experience within this series of dialogs, helping the user to see the context > of the current view and to navigate back up the hierarchy more easily. It > will also be more consistent with the overall UX of Ambari 3.0.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21950) Package Installation is failing If Patch-VDF contain service that is not installed in the cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166609#comment-16166609 ] Hudson commented on AMBARI-21950: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #212 (See [https://builds.apache.org/job/Ambari-branch-2.6/212/]) AMBARI-21950. Package Installation is failing If Patch-VDF contain (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1dd39299d21c48e98b5e4b72c36e4105418a7e4e]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java > Package Installation is failing If Patch-VDF contain service that is not > installed in the cluster. > -- > > Key: AMBARI-21950 > URL: https://issues.apache.org/jira/browse/AMBARI-21950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21950.patch > > > The BE is checking for services in the cluster after it marks hosts as > INSTALLING -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166610#comment-16166610
]
Hudson commented on AMBARI-21940:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #212 (See
[https://builds.apache.org/job/Ambari-branch-2.6/212/])
AMBARI-21940. Ambari schema upgrade from any version older than 2.5.1
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6407f9329ed6ece32ba64d92205f164eb2b8732d])
* (add)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog2402.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelperTest.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21940.patch, AMBARI-21940.patch
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21948) Final flag is available for a property which is 'Undefined' in Default config group
[ https://issues.apache.org/jira/browse/AMBARI-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166608#comment-16166608 ] Hudson commented on AMBARI-21948: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #212 (See [https://builds.apache.org/job/Ambari-branch-2.6/212/]) AMBARI-21948. Final flag is available for a property which is (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4124b118ad2df1972587ebbc05af50317735d8d2]) * (edit) ambari-web/app/views/common/configs/controls_view.js > Final flag is available for a property which is 'Undefined' in Default config > group > --- > > Key: AMBARI-21948 > URL: https://issues.apache.org/jira/browse/AMBARI-21948 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21948_branch-2.6.patch, AMBARI-21948.patch > > > When you switch to new config group, it shows the current value of property > in Default config group which is 'Undefined', but it has a 'Final' flag > option available too. > Doesn't look like its expected because even if you try to set the flag for > 'Undefined' Save button is not enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[
https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166578#comment-16166578
]
Hadoop QA commented on AMBARI-21960:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887117/AMBARI-21960.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12218//console
This message is automatically generated.
> Cluster provision should allow repo version and repo version id be null to
> allow default stack version deployment
> -
>
> Key: AMBARI-21960
> URL: https://issues.apache.org/jira/browse/AMBARI-21960
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21960.patch
>
>
> Remove repository_version and repository_version_id null checks for BP
> deployments
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21885: -- Attachment: AMBARI-21885.patch > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > Attachments: AMBARI-21885.patch > > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166565#comment-16166565 ] Andrii Tkach commented on AMBARI-21885: --- branch-2.6: 30490 passing (26s) 157 pending > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > Attachments: AMBARI-21885.patch > > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21885: -- Status: Patch Available (was: Open) > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > Attachments: AMBARI-21885.patch > > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21885) Config group filter in Dashboard page shows 'All' even if you choose a config group
[ https://issues.apache.org/jira/browse/AMBARI-21885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach reassigned AMBARI-21885: - Assignee: Andrii Tkach > Config group filter in Dashboard page shows 'All' even if you choose a config > group > --- > > Key: AMBARI-21885 > URL: https://issues.apache.org/jira/browse/AMBARI-21885 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Andrii Tkach > > - Naviagte to Config History tab in dashboard page. > - From the dropdown for config groups select a conf group name. Even though > the config group is selected fine, UI shows All -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21960: --- Status: Patch Available (was: Open) > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id null checks for BP > deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21958) Fix broken zeppelin python unit test
[ https://issues.apache.org/jira/browse/AMBARI-21958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21958: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix broken zeppelin python unit test > > > Key: AMBARI-21958 > URL: https://issues.apache.org/jira/browse/AMBARI-21958 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0 > > Attachments: AMBARI-21958_trunk_v1.patch, AMBARI-21958_trunk_v2.patch > > > test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be > happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21958) Fix broken zeppelin python unit test
[ https://issues.apache.org/jira/browse/AMBARI-21958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21958: - Attachment: AMBARI-21958_trunk_v2.patch > Fix broken zeppelin python unit test > > > Key: AMBARI-21958 > URL: https://issues.apache.org/jira/browse/AMBARI-21958 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0 > > Attachments: AMBARI-21958_trunk_v1.patch, AMBARI-21958_trunk_v2.patch > > > test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be > happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21940:
Resolution: Fixed
Status: Resolved (was: Patch Available)
To https://git-wip-us.apache.org/repos/asf/ambari.git
1dd39299d2..6407f9329e branch-2.6 -> branch-2.6
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21940.patch, AMBARI-21940.patch
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21945) Refresh Include/Exclude breaks parallel operations and can't be turned off
[ https://issues.apache.org/jira/browse/AMBARI-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21945: Attachment: AMBARI-21945_2.patch > Refresh Include/Exclude breaks parallel operations and can't be turned off > -- > > Key: AMBARI-21945 > URL: https://issues.apache.org/jira/browse/AMBARI-21945 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.6.0 > > Attachments: AMBARI-21945_2.patch, AMBARI-21945.patch > > > Each time a new server is registered, there is an operation to refresh HDFS > and YARN exclude file and now the operations (install components + start > components) in Ambari can not be executed in parallel b/c refresh exclude > file is an atomic process. Each server's operations of install and start > components processes have to await previous one's refresh node to be > finished. This means adding servers through blueprint is extremely slow now > when many servers are being launched at the similar time. > Also the refresh exclude file for each servers are still being executed even > when 'manage.include.files' flags are turned off in yarn-site and hdfs-site. > Previously in 2.5.1 we mange refresh files after adding / removing each batch > of the servers, now seems this is impossible in 2.5.2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21960: --- Attachment: AMBARI-21960.patch > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id checks for BP deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
[ https://issues.apache.org/jira/browse/AMBARI-21960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21960: --- Description: Remove repository_version and repository_version_id null checks for BP deployments (was: Remove repository_version and repository_version_id checks for BP deployments) > Cluster provision should allow repo version and repo version id be null to > allow default stack version deployment > - > > Key: AMBARI-21960 > URL: https://issues.apache.org/jira/browse/AMBARI-21960 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21960.patch > > > Remove repository_version and repository_version_id null checks for BP > deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21960) Cluster provision should allow repo version and repo version id be null to allow default stack version deployment
Nate Cole created AMBARI-21960: -- Summary: Cluster provision should allow repo version and repo version id be null to allow default stack version deployment Key: AMBARI-21960 URL: https://issues.apache.org/jira/browse/AMBARI-21960 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.6.0 Remove repository_version and repository_version_id checks for BP deployments -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21950) Package Installation is failing If Patch-VDF contain service that is not installed in the cluster.
[ https://issues.apache.org/jira/browse/AMBARI-21950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21950: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Package Installation is failing If Patch-VDF contain service that is not > installed in the cluster. > -- > > Key: AMBARI-21950 > URL: https://issues.apache.org/jira/browse/AMBARI-21950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21950.patch > > > The BE is checking for services in the cluster after it marks hosts as > INSTALLING -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21933) Implement breadcrumbs in Background Operations modal
[ https://issues.apache.org/jira/browse/AMBARI-21933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb updated AMBARI-21933: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Implement breadcrumbs in Background Operations modal > > > Key: AMBARI-21933 > URL: https://issues.apache.org/jira/browse/AMBARI-21933 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb > Fix For: 3.0.0 > > Attachments: AMBARI-21933.patch > > > Implement breadcrumb navigation in the Background Operations modal and the > drill-down views within it. This also affects the use of these views in the > High Availability wizard. The breadcrumbs will provide a better navigation > experience within this series of dialogs, helping the user to see the context > of the current view and to navigate back up the hierarchy more easily. It > will also be more consistent with the overall UX of Ambari 3.0.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21959:
-
Attachment: AMBARI-21959.patch
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21959_branch-2.6.patch, AMBARI-21959.patch
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21959:
-
Status: Patch Available (was: Open)
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21959_branch-2.6.patch, AMBARI-21959.patch
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21959:
-
Attachment: AMBARI-21959_branch-2.6.patch
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21959_branch-2.6.patch, AMBARI-21959.patch
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21940:
Attachment: AMBARI-21940.patch
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21940.patch, AMBARI-21940.patch
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21940:
Status: Patch Available (was: Open)
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21940.patch
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21940:
Attachment: AMBARI-21940.patch
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
> Attachments: AMBARI-21940.patch
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21940) Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check
[
https://issues.apache.org/jira/browse/AMBARI-21940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko reassigned AMBARI-21940:
---
Assignee: Dmitry Lysnichenko
> Ambari schema upgrade from any version older than 2.5.1 fails due to
> incorrect version check
> -
>
> Key: AMBARI-21940
> URL: https://issues.apache.org/jira/browse/AMBARI-21940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.6.0
>
>
> Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x)
> to 2.6.0
> Fails with below error
> {code}
> 12 Sep 2017 02:16:35,727 INFO [main] TransactionalLock$LockArea:121 -
> LockArea HRC_STATUS_CACHE is enabled
> 12 Sep 2017 02:16:36,091 INFO [main] LockFactory:53 - Lock profiling is
> disabled
> 12 Sep 2017 02:16:36,112 INFO [main] SchemaUpgradeHelper:391 - Upgrading
> schema to target version = 2.6.0.0
> 12 Sep 2017 02:16:36,115 INFO [main] SchemaUpgradeHelper:400 - Upgrading
> schema from source version = 2.5.0
> 12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Database version does not meet
> minimal upgrade requirements. Expected version should be not less than 2.5.1,
> current version is 2.5.0
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
> 12 Sep 2017 02:16:40,419 INFO [main] Configuration:3044 - Reading password
> from existing file
> 12 Sep 2017 02:16:40,439 INFO [main] Configuration:3529 - Hosts Mapping File
> null
> 12 Sep 2017 02:16:40,439 INFO [main] HostsMap:60 - Using hostsmap file null
> 12 Sep 2017 02:16:41,290 INFO [main] ControllerModule:221 - Detected MYSQL
> as the database type from the JDBC URL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation
[
https://issues.apache.org/jira/browse/AMBARI-21959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-21959:
-
Summary: [Intermittent] Clicking Next from Customize Services -> Misc tab
does not load the Review page while installation (was: [Intermittent] Clicking
Next from Customize Services -> Misc tab does not load the Review page while
installation of Perf stack)
> [Intermittent] Clicking Next from Customize Services -> Misc tab does not
> load the Review page while installation
> -
>
> Key: AMBARI-21959
> URL: https://issues.apache.org/jira/browse/AMBARI-21959
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.0
>
>
> During installation, clicking on Next in Customize Services Page-> Misc does
> not load the Review Page even after a reasonable amount of time.
> There are javascript errors:
> {code:javascript}
> Uncaught TypeError: Cannot read property 'value' of undefined
> at Class. (app.js:200556)
> at ComputedPropertyPrototype.get (vendor.js:4608)
> at Object.get (vendor.js:3014)
> at Ember.Handlebars.getPath (vendor.js:19671)
> at Class. (vendor.js:19928)
> at ComputedPropertyPrototype.get (vendor.js:4613)
> at get (vendor.js:3014)
> at Class.render (vendor.js:19968)
> at Class.newFunc (vendor.js:2608)
> at Class.render (app.js:186103)
> (anonymous) @ app.js:200556
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21959) [Intermittent] Clicking Next from Customize Services -> Misc tab does not load the Review page while installation of Perf stack
Aleksandr Kovalenko created AMBARI-21959:
Summary: [Intermittent] Clicking Next from Customize Services ->
Misc tab does not load the Review page while installation of Perf stack
Key: AMBARI-21959
URL: https://issues.apache.org/jira/browse/AMBARI-21959
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.2
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
Fix For: 2.6.0
During installation, clicking on Next in Customize Services Page-> Misc does
not load the Review Page even after a reasonable amount of time.
There are javascript errors:
{code:javascript}
Uncaught TypeError: Cannot read property 'value' of undefined
at Class. (app.js:200556)
at ComputedPropertyPrototype.get (vendor.js:4608)
at Object.get (vendor.js:3014)
at Ember.Handlebars.getPath (vendor.js:19671)
at Class. (vendor.js:19928)
at ComputedPropertyPrototype.get (vendor.js:4613)
at get (vendor.js:3014)
at Class.render (vendor.js:19968)
at Class.newFunc (vendor.js:2608)
at Class.render (app.js:186103)
(anonymous) @ app.js:200556
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21901) Add 0.7.x stack definition for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21901: - Attachment: AMBARI-21901_master_v4.patch > Add 0.7.x stack definition for Zeppelin > --- > > Key: AMBARI-21901 > URL: https://issues.apache.org/jira/browse/AMBARI-21901 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21901_branch-0.6_v3.patch, > AMBARI-21901_master_v3.patch, AMBARI-21901_master_v4.patch, > AMBARI-21901_trunk_v1.patch, AMBARI-21901_trunk_v2.patch > > > Currently, in Zeppelin, there are two stack definitions 0.6.0.2.5 and > 0.6.0.3.0. The ideas of this Jira are following: > - rename 0.6.0.2.5 to 0.6.0 > - delete redundant 0.6.0.3.0 > - create another defination for 0.7.x as 0.7.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21958) Fix broken zeppelin python unit test
[ https://issues.apache.org/jira/browse/AMBARI-21958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21958: - Attachment: AMBARI-21958_trunk_v1.patch > Fix broken zeppelin python unit test > > > Key: AMBARI-21958 > URL: https://issues.apache.org/jira/browse/AMBARI-21958 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0 > > Attachments: AMBARI-21958_trunk_v1.patch > > > test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be > happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21958) Fix broken zeppelin python unit test
[ https://issues.apache.org/jira/browse/AMBARI-21958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21958: - Status: Patch Available (was: Open) > Fix broken zeppelin python unit test > > > Key: AMBARI-21958 > URL: https://issues.apache.org/jira/browse/AMBARI-21958 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0 > > > test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be > happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21958) Fix broken zeppelin python unit test
Prabhjyot Singh created AMBARI-21958: Summary: Fix broken zeppelin python unit test Key: AMBARI-21958 URL: https://issues.apache.org/jira/browse/AMBARI-21958 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh Fix For: 3.0.0 test_start_secured (test_zeppelin_master.TestZeppelinMaster) seems to be happening after AMBARI-21814 commit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21957: - Status: Patch Available (was: In Progress) > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21957.patch > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21957: - Attachment: AMBARI-21957.patch > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21957.patch > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21957) UI should handle rejection of PATCH VDF
Antonenko Alexander created AMBARI-21957: Summary: UI should handle rejection of PATCH VDF Key: AMBARI-21957 URL: https://issues.apache.org/jira/browse/AMBARI-21957 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 As of now, UI just breaks when VDF is rejected STR # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 # Register the attached VDF # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21957) UI should handle rejection of PATCH VDF
[ https://issues.apache.org/jira/browse/AMBARI-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21957: Assignee: Antonenko Alexander > UI should handle rejection of PATCH VDF > --- > > Key: AMBARI-21957 > URL: https://issues.apache.org/jira/browse/AMBARI-21957 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > > As of now, UI just breaks when VDF is rejected > STR > # Install ZooKeeper, HDFS on HDP 2.6.0.1-207 > # Register the attached VDF > # Try to start upgrade -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21948) Final flag is available for a property which is 'Undefined' in Default config group
[ https://issues.apache.org/jira/browse/AMBARI-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-21948: - Resolution: Fixed Status: Resolved (was: Patch Available) > Final flag is available for a property which is 'Undefined' in Default config > group > --- > > Key: AMBARI-21948 > URL: https://issues.apache.org/jira/browse/AMBARI-21948 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21948_branch-2.6.patch, AMBARI-21948.patch > > > When you switch to new config group, it shows the current value of property > in Default config group which is 'Undefined', but it has a 'Final' flag > option available too. > Doesn't look like its expected because even if you try to set the flag for > 'Undefined' Save button is not enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21948) Final flag is available for a property which is 'Undefined' in Default config group
[ https://issues.apache.org/jira/browse/AMBARI-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166064#comment-16166064 ] Aleksandr Kovalenko commented on AMBARI-21948: -- committed to trunk and branch-2.6 > Final flag is available for a property which is 'Undefined' in Default config > group > --- > > Key: AMBARI-21948 > URL: https://issues.apache.org/jira/browse/AMBARI-21948 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21948_branch-2.6.patch, AMBARI-21948.patch > > > When you switch to new config group, it shows the current value of property > in Default config group which is 'Undefined', but it has a 'Final' flag > option available too. > Doesn't look like its expected because even if you try to set the flag for > 'Undefined' Save button is not enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21922) Allow SERVER Type Alerts To Run For Any Service/Component
[
https://issues.apache.org/jira/browse/AMBARI-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-21922:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow SERVER Type Alerts To Run For Any Service/Component
> -
>
> Key: AMBARI-21922
> URL: https://issues.apache.org/jira/browse/AMBARI-21922
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0, 2.6.0
>
> Attachments: AMBARI-21922.patch
>
>
> There is a type of alert known as a "SERVER" alert which is a Java class that
> runs inside of the Ambari Server. We use these alerts to check for specific
> issues with the Ambari Server itself.
> However, nothing should prevent a cluster's services from being able to
> define one of these. Consider the following case where we want a new
> server-side alert to run for the ZooKeeper Service which checks something
> specific that none of the agent-side alerts are appropriate for:
> {code}
> {
> "ZOOKEEPER": {
> "service": [
> {
> "name": "Foo",
> "label": "Foo ZK Alert",
> "description": "Foo",
> "interval": 5,
> "scope": "SERVICE",
> "enabled": true,
> "source": {
> "type": "SERVER",
> "class": "org.apache.ambari.server.alerts.ZKFooChecker"
> }
> }
> ],
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21901) Add 0.7.x stack definition for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21901: - Attachment: AMBARI-21901_branch-0.6_v3.patch AMBARI-21901_master_v3.patch > Add 0.7.x stack definition for Zeppelin > --- > > Key: AMBARI-21901 > URL: https://issues.apache.org/jira/browse/AMBARI-21901 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21901_branch-0.6_v3.patch, > AMBARI-21901_master_v3.patch, AMBARI-21901_trunk_v1.patch, > AMBARI-21901_trunk_v2.patch > > > Currently, in Zeppelin, there are two stack definitions 0.6.0.2.5 and > 0.6.0.3.0. The ideas of this Jira are following: > - rename 0.6.0.2.5 to 0.6.0 > - delete redundant 0.6.0.3.0 > - create another defination for 0.7.x as 0.7.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21956) Make Ambari user/group search case insensitive
Hari Sekhon created AMBARI-21956: Summary: Make Ambari user/group search case insensitive Key: AMBARI-21956 URL: https://issues.apache.org/jira/browse/AMBARI-21956 Project: Ambari Issue Type: Improvement Affects Versions: 2.5.1 Environment: HDP 2.6 Reporter: Hari Sekhon Priority: Minor Improvement request to make Ambari user/group search case insensitive in the manage Ambari users section. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Port Storm View from React.js to Vue.js
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shah updated AMBARI-21955: - Attachment: AMBARI-21955.patch > Port Storm View from React.js to Vue.js > --- > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Port Storm View from React.js to Vue.js
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shah updated AMBARI-21955: - Attachment: (was: AMBARI-21955.patch) > Port Storm View from React.js to Vue.js > --- > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Port Storm View from React.js to Vue.js
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shah updated AMBARI-21955: - Affects Version/s: 2.6.0 > Port Storm View from React.js to Vue.js > --- > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Port Storm View from React.js to Vue.js
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shah updated AMBARI-21955: - Attachment: AMBARI-21955.patch > Port Storm View from React.js to Vue.js > --- > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Port Storm View from React.js to Vue.js
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shah updated AMBARI-21955: - Status: Patch Available (was: In Progress) > Port Storm View from React.js to Vue.js > --- > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
