[jira] [Commented] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717637#comment-15717637
]
Hudson commented on AMBARI-19073:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6150 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6150/])
AMBARI-19073 - Ambari Contrib View Has Inconsistent Version in pom.xml
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3096c79dfa666341154d70a7b5a0b61eb7696d52])
* (edit) contrib/views/ambari-views-package/pom.xml
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-19073.patch
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717591#comment-15717591 ] Hudson commented on AMBARI-19070: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6149 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6149/]) AMBARI-19070. Incorrect version metadata for HDP 2.6 (smohanty) (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2f6942f5b6d09e07ed31e28ed70a741db899fbc7]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/FLUME/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ACCUMULO/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SLIDER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/FALCON/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/OOZIE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER_KMS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/KNOX/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/PIG/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/MAHOUT/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZOOKEEPER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SQOOP/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-18966:
---
Attachment: AMBARI-18966.patch
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18966) Add check to ensure we do not have @Transactional annotations on private methods
[
https://issues.apache.org/jira/browse/AMBARI-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-18966:
---
Attachment: (was: AMBARI-18966.patch)
> Add check to ensure we do not have @Transactional annotations on private
> methods
>
>
> Key: AMBARI-18966
> URL: https://issues.apache.org/jira/browse/AMBARI-18966
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18966.patch
>
>
> {{@Transactional}} methods [must not be
> {{private}}|https://github.com/google/guice/wiki/Transactions#method-level-transactional].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
[
https://issues.apache.org/jira/browse/AMBARI-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717307#comment-15717307
]
Hadoop QA commented on AMBARI-19072:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841599/AMBARI-19072.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9514//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9514//console
This message is automatically generated.
> Cannot set/change Status and Ambari Admin toggle buttons when creating or
> editing users
> ---
>
> Key: AMBARI-19072
> URL: https://issues.apache.org/jira/browse/AMBARI-19072
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: trunk, 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
> Attachments: AMBARI-19072.patch, EditUser.jpg
>
>
> 1. In Ambari Admin view, click on Creat Local User or click on an existing
> user.
> 2. The Status and Ambari Admin toggle buttons cannot be changed.
> Underlying error:
> "Error: [$compile:ctreq] Controller 'ngModel', required by directive
> 'toggleSwitch', can't be found!
> http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19073:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-19073.patch
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717283#comment-15717283 ] Hudson commented on AMBARI-19070: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #449 (See [https://builds.apache.org/job/Ambari-branch-2.5/449/]) AMBARI-19070. Incorrect version metadata for HDP 2.6 (smohanty) (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=32af20930eec5ba0a386edcdd0418cb46a39d9bb]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER_KMS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/OOZIE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/FLUME/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/KNOX/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/PIG/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SLIDER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ACCUMULO/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/FALCON/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/TEZ/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/MAHOUT/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZOOKEEPER/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SQOOP/metainfo.xml > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717280#comment-15717280
]
Hadoop QA commented on AMBARI-19073:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841608/AMBARI-19073.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/9513//console
This message is automatically generated.
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-19073.patch
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19074) Host-Ordered: Empty groups are returned for Downgrade
Nate Cole created AMBARI-19074:
--
Summary: Host-Ordered: Empty groups are returned for Downgrade
Key: AMBARI-19074
URL: https://issues.apache.org/jira/browse/AMBARI-19074
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
Fix For: 2.5.0
When issuing a downgrade for HOU, the server is responding with an error:
{noformat}
org.apache.ambari.server.AmbariException: There are no groupings available
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-19070. Resolution: Fixed committed to trunk and branch-2.5 > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19073:
-
Attachment: AMBARI-19073.patch
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-19073.patch
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19073:
-
Assignee: Jonathan Hurley
Status: Patch Available (was: Open)
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[
https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19073:
-
Description:
{{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
which can cause build failures under certain conditions. The parent POM from
{{contrib/views/pom.xml}} defines 2.0.0.0.0 while
{{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
{code}
git diff pom.xml
diff --git a/contrib/views/ambari-views-package/pom.xml
b/contrib/views/ambari-views-package/pom.xml
index cb070e6..16c9985 100644
--- a/contrib/views/ambari-views-package/pom.xml
+++ b/contrib/views/ambari-views-package/pom.xml
@@ -26,7 +26,7 @@
org.apache.ambari.contrib.views
ambari-contrib-views
-2.5.0.0.0
+2.0.0.0-SNAPSHOT
{code}
This now matches {{contrib/views/pom.xml}}:}
{code}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
org.apache.ambari
ambari-project
2.0.0.0-SNAPSHOT
../../ambari-project
{code}
> Ambari Contrib View Has Inconsistent Version in pom.xml
> ---
>
> Key: AMBARI-19073
> URL: https://issues.apache.org/jira/browse/AMBARI-19073
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
>
> {{contrib/views/ambari-views-package/pom.xml}} has the wrong version defined
> which can cause build failures under certain conditions. The parent POM from
> {{contrib/views/pom.xml}} defines 2.0.0.0.0 while
> {{contrib/views/ambari-views-package/pom.xml}} defines 2.5.0.0.0.
> {code}
> git diff pom.xml
> diff --git a/contrib/views/ambari-views-package/pom.xml
> b/contrib/views/ambari-views-package/pom.xml
> index cb070e6..16c9985 100644
> --- a/contrib/views/ambari-views-package/pom.xml
> +++ b/contrib/views/ambari-views-package/pom.xml
> @@ -26,7 +26,7 @@
>
> org.apache.ambari.contrib.views
> ambari-contrib-views
> -2.5.0.0.0
> +2.0.0.0-SNAPSHOT
>
> {code}
> This now matches {{contrib/views/pom.xml}}:}
> {code}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
> org.apache.ambari
> ambari-project
> 2.0.0.0-SNAPSHOT
> ../../ambari-project
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
[ https://issues.apache.org/jira/browse/AMBARI-19073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-19073: - Fix Version/s: trunk > Ambari Contrib View Has Inconsistent Version in pom.xml > --- > > Key: AMBARI-19073 > URL: https://issues.apache.org/jira/browse/AMBARI-19073 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: trunk >Reporter: Jonathan Hurley >Priority: Critical > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19073) Ambari Contrib View Has Inconsistent Version in pom.xml
Jonathan Hurley created AMBARI-19073: Summary: Ambari Contrib View Has Inconsistent Version in pom.xml Key: AMBARI-19073 URL: https://issues.apache.org/jira/browse/AMBARI-19073 Project: Ambari Issue Type: Bug Components: contrib Affects Versions: trunk Reporter: Jonathan Hurley Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717037#comment-15717037
]
Hudson commented on AMBARI-19071:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6148 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6148/])
AMBARI-19071. Ambari Server Unit Test failure on branch-2.5 and trunk:
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6c411baa2f3d9bae5ba7e781ac3b4cddbf18ae82])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/configuration/zk-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/configuration/hdfs-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/configuration/hbase-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-alert-config.xml
> Ambari Server Unit Test failure on branch-2.5 and trunk:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-19071
> URL: https://issues.apache.org/jira/browse/AMBARI-19071
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19071.patch
>
>
> This error is happening on both trunk and branch-2.5.
> {code}
> Running org.apache.ambari.server.state.ServiceTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
> FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 7.281 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
> value-attributes, depends-on, property_depended_by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
[ https://issues.apache.org/jira/browse/AMBARI-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19072: Fix Version/s: trunk Status: Patch Available (was: In Progress) > Cannot set/change Status and Ambari Admin toggle buttons when creating or > editing users > --- > > Key: AMBARI-19072 > URL: https://issues.apache.org/jira/browse/AMBARI-19072 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-19072.patch, EditUser.jpg > > > 1. In Ambari Admin view, click on Creat Local User or click on an existing > user. > 2. The Status and Ambari Admin toggle buttons cannot be changed. > Underlying error: > "Error: [$compile:ctreq] Controller 'ngModel', required by directive > 'toggleSwitch', can't be found! > http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
[ https://issues.apache.org/jira/browse/AMBARI-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19072: Attachment: AMBARI-19072.patch > Cannot set/change Status and Ambari Admin toggle buttons when creating or > editing users > --- > > Key: AMBARI-19072 > URL: https://issues.apache.org/jira/browse/AMBARI-19072 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-19072.patch, EditUser.jpg > > > 1. In Ambari Admin view, click on Creat Local User or click on an existing > user. > 2. The Status and Ambari Admin toggle buttons cannot be changed. > Underlying error: > "Error: [$compile:ctreq] Controller 'ngModel', required by directive > 'toggleSwitch', can't be found! > http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
[ https://issues.apache.org/jira/browse/AMBARI-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19072: Attachment: EditUser.jpg > Cannot set/change Status and Ambari Admin toggle buttons when creating or > editing users > --- > > Key: AMBARI-19072 > URL: https://issues.apache.org/jira/browse/AMBARI-19072 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: EditUser.jpg > > > 1. In Ambari Admin view, click on Creat Local User or click on an existing > user. > 2. The Status and Ambari Admin toggle buttons cannot be changed. > Underlying error: > "Error: [$compile:ctreq] Controller 'ngModel', required by directive > 'toggleSwitch', can't be found! > http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716980#comment-15716980
]
Hudson commented on AMBARI-19071:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #448 (See
[https://builds.apache.org/job/Ambari-branch-2.5/448/])
AMBARI-19071. Ambari Server Unit Test failure on branch-2.5 and trunk:
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0462cf95434c70a5d8a64fe02d6ff94eac021c5a])
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/configuration/yarn-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/configuration/hbase-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/configuration/zk-alert-config.xml
* (edit)
ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/configuration/hdfs-alert-config.xml
> Ambari Server Unit Test failure on branch-2.5 and trunk:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-19071
> URL: https://issues.apache.org/jira/browse/AMBARI-19071
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19071.patch
>
>
> This error is happening on both trunk and branch-2.5.
> {code}
> Running org.apache.ambari.server.state.ServiceTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
> FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 7.281 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
> value-attributes, depends-on, property_depended_by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
Sangeeta Ravindran created AMBARI-19072: --- Summary: Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users Key: AMBARI-19072 URL: https://issues.apache.org/jira/browse/AMBARI-19072 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: trunk, 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran 1. In Ambari Admin view, click on Creat Local User. 2. The Status and Ambari Admin toggle buttons cannot be changed. Underlying error: "Error: [$compile:ctreq] Controller 'ngModel', required by directive 'toggleSwitch', can't be found! http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19072) Cannot set/change Status and Ambari Admin toggle buttons when creating or editing users
[ https://issues.apache.org/jira/browse/AMBARI-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19072: Description: 1. In Ambari Admin view, click on Creat Local User or click on an existing user. 2. The Status and Ambari Admin toggle buttons cannot be changed. Underlying error: "Error: [$compile:ctreq] Controller 'ngModel', required by directive 'toggleSwitch', can't be found! http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch was: 1. In Ambari Admin view, click on Creat Local User. 2. The Status and Ambari Admin toggle buttons cannot be changed. Underlying error: "Error: [$compile:ctreq] Controller 'ngModel', required by directive 'toggleSwitch', can't be found! http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch > Cannot set/change Status and Ambari Admin toggle buttons when creating or > editing users > --- > > Key: AMBARI-19072 > URL: https://issues.apache.org/jira/browse/AMBARI-19072 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > > 1. In Ambari Admin view, click on Creat Local User or click on an existing > user. > 2. The Status and Ambari Admin toggle buttons cannot be changed. > Underlying error: > "Error: [$compile:ctreq] Controller 'ngModel', required by directive > 'toggleSwitch', can't be found! > http://errors.angularjs.org/1.2.26/$compile/ctreq?p0=ngModel=toggleSwitch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs
[ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19058: --- Attachment: (was: AMBARI-19058_part1.patch) > Perf: Deploy 3000 Agent cluster and find perf bugs > -- > > Key: AMBARI-19058 > URL: https://issues.apache.org/jira/browse/AMBARI-19058 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-19058_part1.patch > > > Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and > start finding perf bugs in the following areas. > Agent registration (batches of 600 at a time are still very slow) > Alerts > Commands like starting/restarting/rolling restart, etc. > Memory leaks after letting it run for a week? > We may need to also run a memory profiler on the java process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs
[ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19058: --- Attachment: AMBARI-19058_part1.patch > Perf: Deploy 3000 Agent cluster and find perf bugs > -- > > Key: AMBARI-19058 > URL: https://issues.apache.org/jira/browse/AMBARI-19058 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-19058_part1.patch, AMBARI-19058_part1.patch > > > Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and > start finding perf bugs in the following areas. > Agent registration (batches of 600 at a time are still very slow) > Alerts > Commands like starting/restarting/rolling restart, etc. > Memory leaks after letting it run for a week? > We may need to also run a memory profiler on the java process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716943#comment-15716943 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6147 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6147/]) Revert "Revert "AMBARI-1: Ambari-agent: Create configuration files (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=db46822fbf50c5e5222bdec094b3a011584f8ee8]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/conf/unix/ambari-agent.ini > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19071:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Ambari Server Unit Test failure on branch-2.5 and trunk:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-19071
> URL: https://issues.apache.org/jira/browse/AMBARI-19071
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19071.patch
>
>
> This error is happening on both trunk and branch-2.5.
> {code}
> Running org.apache.ambari.server.state.ServiceTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
> FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 7.281 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
> value-attributes, depends-on, property_depended_by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19071:
---
Attachment: AMBARI-19071.patch
> Ambari Server Unit Test failure on branch-2.5 and trunk:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-19071
> URL: https://issues.apache.org/jira/browse/AMBARI-19071
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19071.patch
>
>
> This error is happening on both trunk and branch-2.5.
> {code}
> Running org.apache.ambari.server.state.ServiceTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
> FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 7.281 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
> value-attributes, depends-on, property_depended_by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
[
https://issues.apache.org/jira/browse/AMBARI-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19071:
---
Status: Patch Available (was: Open)
> Ambari Server Unit Test failure on branch-2.5 and trunk:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
> -
>
> Key: AMBARI-19071
> URL: https://issues.apache.org/jira/browse/AMBARI-19071
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19071.patch
>
>
> This error is happening on both trunk and branch-2.5.
> {code}
> Running org.apache.ambari.server.state.ServiceTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
> FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 7.281 sec <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
> value-attributes, depends-on, property_depended_by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19071) Ambari Server Unit Test failure on branch-2.5 and trunk: org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
Vitaly Brodetskyi created AMBARI-19071:
--
Summary: Ambari Server Unit Test failure on branch-2.5 and trunk:
org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs
Key: AMBARI-19071
URL: https://issues.apache.org/jira/browse/AMBARI-19071
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.5.0
This error is happening on both trunk and branch-2.5.
{code}
Running org.apache.ambari.server.state.ServiceTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.352 sec <<<
FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
Time elapsed: 7.281 sec <<< ERROR!
org.apache.ambari.server.AmbariException: File
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-alert-config.xml
didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
content of element 'property' is not complete. One of '{display-name, filename,
deleted, final, on-ambari-upgrade, on-stack-upgrade, property-type,
value-attributes, depends-on, property_depended_by}' is expected.
at
org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:50)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716844#comment-15716844 ] Hudson commented on AMBARI-19069: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6146 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6146/]) AMBARI-19069. Remove 'llap_queue_capacity' references from UI code. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e465c0e7a667e8c411a1ff38480bddd49e01427c]) * (edit) ambari-web/app/models/configs/objects/service_config_property.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/common/configs/widgets/slider_config_widget_view.js > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19069.patch > > > Config 'llap_queue_capacity' exists in hive-interactive-env. But with > AMBARI-18901 work, this config will be removed. > ambari-web should also remove any special handling that it does with > 'llap_queue_capacity' as of now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716832#comment-15716832 ] Yusaku Sako commented on AMBARI-19070: -- +1 > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716832#comment-15716832 ] Yusaku Sako edited comment on AMBARI-19070 at 12/2/16 11:17 PM: +1 for the patch was (Author: u39kun): +1 > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19070) Incorrect version metadata for HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19070: --- Attachment: AMBARI-19070.patch [~u39kun] can you review? > Incorrect version metadata for HDP 2.6 > -- > > Key: AMBARI-19070 > URL: https://issues.apache.org/jira/browse/AMBARI-19070 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19070.patch > > > Fix the default version value in HDP stack. VDFs, when available, provide the > correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19070) Incorrect version metadata for HDP 2.6
Sumit Mohanty created AMBARI-19070: -- Summary: Incorrect version metadata for HDP 2.6 Key: AMBARI-19070 URL: https://issues.apache.org/jira/browse/AMBARI-19070 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.5.0 Fix the default version value in HDP stack. VDFs, when available, provide the correct value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716813#comment-15716813 ] Hudson commented on AMBARI-19068: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #447 (See [https://builds.apache.org/job/Ambari-branch-2.5/447/]) AMBARI-19068. Logsearch has a 'required' property while adding Ranger (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e7c2fdd700e2c3f734e4a8ca7d8e88048b8e400e]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716791#comment-15716791 ] Hudson commented on AMBARI-19068: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6145 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6145/]) AMBARI-19068. Logsearch has a 'required' property while adding Ranger (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5901b95bc3c4d718b7e7723baf403f3d5522647a]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[
https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716776#comment-15716776
]
Hadoop QA commented on AMBARI-19069:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841573/AMBARI-19069.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/9512//console
This message is automatically generated.
> Remove 'llap_queue_capacity' references from UI code.
> -
>
> Key: AMBARI-19069
> URL: https://issues.apache.org/jira/browse/AMBARI-19069
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-19069.patch
>
>
> Config 'llap_queue_capacity' exists in hive-interactive-env. But with
> AMBARI-18901 work, this config will be removed.
> ambari-web should also remove any special handling that it does with
> 'llap_queue_capacity' as of now
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716773#comment-15716773
]
Hadoop QA commented on AMBARI-1:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841554/rb53747.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9511//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9511//console
This message is automatically generated.
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Attachments: rb53747.patch
>
>
> When a non-status command is received, a command.json file is generated. This
> file contains the passwords used in a configuration. When the command is then
> executed, ambari agent spawns off a subprocess to execute component-specific
> Python scripts to generate the configuration files using the data from the
> command.json file.
> To avoid storing clear text passwords in command.json file and configuration
> files, ambari-agent will first generate the JCEKS files corresponding to the
> configuration information in the command JSON blob coming from the server and
> then generate the command.json with the path to the JCEKS store instead of
> clear text passwords for *password* properties.
> Subsequently when executing a command, ambari-agent will generate the
> configuration files with the JCEKS path information from command.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716760#comment-15716760 ] Jaimin Jetly commented on AMBARI-19069: --- Received +1 on reviewboard. Patch committed to trunk. Pending to commit in branch-2.5 > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19069.patch > > > Config 'llap_queue_capacity' exists in hive-interactive-env. But with > AMBARI-18901 work, this config will be removed. > ambari-web should also remove any special handling that it does with > 'llap_queue_capacity' as of now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19069: -- Status: Patch Available (was: Open) Verified the patch on the cluster. Verified that the patch does not affect ambari-web unit test run: ambari-web (branch-2.5) unit test result with the patch: 25637 tests complete (23 seconds) 57 tests pending > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19069.patch > > > Config 'llap_queue_capacity' exists in hive-interactive-env. But with > AMBARI-18901 work, this config will be removed. > ambari-web should also remove any special handling that it does with > 'llap_queue_capacity' as of now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19069: -- Attachment: AMBARI-19069.patch > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19069.patch > > > Config 'llap_queue_capacity' exists in hive-interactive-env. But with > AMBARI-18901 work, this config will be removed. > ambari-web should also remove any special handling that it does with > 'llap_queue_capacity' as of now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
[
https://issues.apache.org/jira/browse/AMBARI-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716732#comment-15716732
]
Hudson commented on AMBARI-19055:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #446 (See
[https://builds.apache.org/job/Ambari-branch-2.5/446/])
AMBARI-19055 - Removing Tasks From host_role_command Causes Upgrades To
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=19ca036c683e6d1741f1b6d73a2f3326f3fc20fd])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CalculatedStatusTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
> Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
>
>
> Key: AMBARI-19055
> URL: https://issues.apache.org/jira/browse/AMBARI-19055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19055.patch
>
>
> It may be necessary to remove entries from the {{host_role_command}} table if
> the size of the table has grown excessively large in order to reduce the
> query times for "IN_PROGRESS" requests.
> However, if you remove all tasks for an upgrade, but you leave the stages,
> request, and upgrade items, the upgrade will appear as though it is now
> {{PENDING}}.
> {noformat:title=Before Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "COMPLETED",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> {noformat:title=After Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "PENDING",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> The actual request is showing as {{COMPLETED}} correctly:
> {noformat}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/requests/12;,
> "Requests": {
> "aborted_task_count": 0,
> "cluster_name": "c1",
> "completed_task_count": 0,
> "create_time": 1480517560897,
> "end_time": 1480517643350,
> "exclusive": false,
> "failed_task_count": 0,
> "id": 12,
> "inputs": null,
> "operation_level": null,
> "progress_percent": 100,
> "queued_task_count": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_schedule": null,
> "request_status": "COMPLETED",
> "resource_filters": [],
> "start_time": 1480517560950,
> "task_count": 0,
> "timed_out_task_count": 0,
> "type": "INTERNAL_REQUEST"
> },
> "tasks": [],
> ...
> {noformat}
> STR:
> - Perform a simple upgrade of a ZK-only cluster
> - Find out the ID of the upgrade request (say its 12)
> - Remove tasks
> {code}
> DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
> host_role_command WHERE request_id = 12)
> DELETE FROM host_role_command WHERE request_id = 12
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19069: -- Description: Config 'llap_queue_capacity' exists in hive-interactive-env. But with AMBARI-18901 work, this config will be removed. ambari-web should also remove any special handling that it does with 'llap_queue_capacity' as of now was:Config 'llap_queue_capacity' existed in hive-interactive-env. But with AMBARI-18901 , we wont be having this config anymore. > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > > Config 'llap_queue_capacity' exists in hive-interactive-env. But with > AMBARI-18901 work, this config will be removed. > ambari-web should also remove any special handling that it does with > 'llap_queue_capacity' as of now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
[ https://issues.apache.org/jira/browse/AMBARI-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19069: -- Description: Config 'llap_queue_capacity' existed in hive-interactive-env. But with AMBARI-18901 , we wont be having this config anymore. > Remove 'llap_queue_capacity' references from UI code. > - > > Key: AMBARI-19069 > URL: https://issues.apache.org/jira/browse/AMBARI-19069 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > > Config 'llap_queue_capacity' existed in hive-interactive-env. But with > AMBARI-18901 , we wont be having this config anymore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19069) Remove 'llap_queue_capacity' references from UI code.
Jaimin Jetly created AMBARI-19069: - Summary: Remove 'llap_queue_capacity' references from UI code. Key: AMBARI-19069 URL: https://issues.apache.org/jira/browse/AMBARI-19069 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[
https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716682#comment-15716682
]
Hadoop QA commented on AMBARI-19068:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841556/AMBARI-19068.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9510//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9510//console
This message is automatically generated.
> Logsearch has a 'required' property while adding Ranger which quickly goes
> off upon navigating to the tab
> -
>
> Key: AMBARI-19068
> URL: https://issues.apache.org/jira/browse/AMBARI-19068
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Dhanya Balasundaran
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19068.patch
>
>
> Navigate to Add service wizard to Add Ranger
> At Customize Services Page notcie that Logsearch has a required property
> (which is not expected)
> Navigate to Logsearch tab to check
> Error for required property quickly goes off
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18936) DataNode JVM heap settings should include CMSInitiatingOccupancy
[
https://issues.apache.org/jira/browse/AMBARI-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716654#comment-15716654
]
Hudson commented on AMBARI-18936:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6144 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6144/])
AMBARI-18936. DataNode JVM heap settings should include (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c837a60c6bbe7c6fb7c5586963520957bb4146f])
* (add)
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
> DataNode JVM heap settings should include CMSInitiatingOccupancy
>
>
> Key: AMBARI-18936
> URL: https://issues.apache.org/jira/browse/AMBARI-18936
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.2.2
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-18936.02.patch
>
>
> This is a followup to AMBARI-18694 to fix remaining stack versions:
> ___
> As HDFS-11047 reported, DirectoryScanner does scan by deep copying
> FinalizedReplica. In a deployment with 500,000+ blocks, we've seen the DN
> heap usage being accumulated to high peaks very quickly. Deep copies of
> FinalizedReplica will make DN heap usage even worse if directory scans are
> scheduled more frequently.
> Another factor is that huge number of ScanInfo instances corresponding to
> HDFS blocks are lingering in garbage to eat many heap memories until a full
> GC takes place.
> This proposes adding JVM settings to force GC more frequently to release
> DataNode heap consumed as a result of two aforementioned reasons, i.e. add
> the options to HADOOP_DATANODE_OPTS
> {noformat}
> -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly
> -XX:ConcGCThreads=8 -XX:+UseConcMarkSweepGC
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content
[ https://issues.apache.org/jira/browse/AMBARI-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716647#comment-15716647 ] Hudson commented on AMBARI-19049: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #445 (See [https://builds.apache.org/job/Ambari-branch-2.5/445/]) AMBARI-19049. Alerts Popup displays full error stacktrace instead of (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f39bd6b6c8ca5790f5370c7f910f60d21b5f2c8d]) * (edit) ambari-web/app/controllers/main/service/info/summary.js * (edit) ambari-web/app/templates/main/service/info/service_alert_popup.hbs > Alerts Popup displays full error stacktrace instead of minimal content > -- > > Key: AMBARI-19049 > URL: https://issues.apache.org/jira/browse/AMBARI-19049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-19049.patch, AMBARI-19049_trunk.patch > > > Alerts Popup displays full error stacktrace instead of minimal content > STR: > Navigate to any service page > Click on Alerts button from top right corner of summary panel > The complete error message should be displayed as a tooltip text or minimal > text should be displayed. But the complete stacktrace is displayed in the > popup window which makes the list of alerts look unorganized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18936) DataNode JVM heap settings should include CMSInitiatingOccupancy
[
https://issues.apache.org/jira/browse/AMBARI-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716652#comment-15716652
]
Hudson commented on AMBARI-18936:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #445 (See
[https://builds.apache.org/job/Ambari-branch-2.5/445/])
AMBARI-18936. DataNode JVM heap settings should include (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aec30d56ab0165acbe36272016dacdf24627e793])
* (add)
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
> DataNode JVM heap settings should include CMSInitiatingOccupancy
>
>
> Key: AMBARI-18936
> URL: https://issues.apache.org/jira/browse/AMBARI-18936
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.2.2
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-18936.02.patch
>
>
> This is a followup to AMBARI-18694 to fix remaining stack versions:
> ___
> As HDFS-11047 reported, DirectoryScanner does scan by deep copying
> FinalizedReplica. In a deployment with 500,000+ blocks, we've seen the DN
> heap usage being accumulated to high peaks very quickly. Deep copies of
> FinalizedReplica will make DN heap usage even worse if directory scans are
> scheduled more frequently.
> Another factor is that huge number of ScanInfo instances corresponding to
> HDFS blocks are lingering in garbage to eat many heap memories until a full
> GC takes place.
> This proposes adding JVM settings to force GC more frequently to release
> DataNode heap consumed as a result of two aforementioned reasons, i.e. add
> the options to HADOOP_DATANODE_OPTS
> {noformat}
> -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly
> -XX:ConcGCThreads=8 -XX:+UseConcMarkSweepGC
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716569#comment-15716569 ] Sumit Mohanty commented on AMBARI-19068: LGTM, +1 > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18936) DataNode JVM heap settings should include CMSInitiatingOccupancy
[
https://issues.apache.org/jira/browse/AMBARI-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716534#comment-15716534
]
Sumit Mohanty commented on AMBARI-18936:
LGTM, +1
> DataNode JVM heap settings should include CMSInitiatingOccupancy
>
>
> Key: AMBARI-18936
> URL: https://issues.apache.org/jira/browse/AMBARI-18936
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.2.2
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-18936.02.patch
>
>
> This is a followup to AMBARI-18694 to fix remaining stack versions:
> ___
> As HDFS-11047 reported, DirectoryScanner does scan by deep copying
> FinalizedReplica. In a deployment with 500,000+ blocks, we've seen the DN
> heap usage being accumulated to high peaks very quickly. Deep copies of
> FinalizedReplica will make DN heap usage even worse if directory scans are
> scheduled more frequently.
> Another factor is that huge number of ScanInfo instances corresponding to
> HDFS blocks are lingering in garbage to eat many heap memories until a full
> GC takes place.
> This proposes adding JVM settings to force GC more frequently to release
> DataNode heap consumed as a result of two aforementioned reasons, i.e. add
> the options to HADOOP_DATANODE_OPTS
> {noformat}
> -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly
> -XX:ConcGCThreads=8 -XX:+UseConcMarkSweepGC
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18662) Check that Stack Version and repo URLs match up when registering repo
[ https://issues.apache.org/jira/browse/AMBARI-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716531#comment-15716531 ] Antonenko Alexander commented on AMBARI-18662: -- Based on issue that may occur with custom Base URL reverted this fix > Check that Stack Version and repo URLs match up when registering repo > -- > > Key: AMBARI-18662 > URL: https://issues.apache.org/jira/browse/AMBARI-18662 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-18662.patch > > > Right now there's no validation when registering a repo to catch these type > of user errors, which caused a lot of problems down the road. We should have > very basic validation using JS so that if we detect a number like "2.5.0.0" > we ensure that the selected stack is also HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content
[ https://issues.apache.org/jira/browse/AMBARI-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19049: - Resolution: Fixed Status: Resolved (was: Patch Available) pushed to 2.5 and trunk > Alerts Popup displays full error stacktrace instead of minimal content > -- > > Key: AMBARI-19049 > URL: https://issues.apache.org/jira/browse/AMBARI-19049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-19049.patch, AMBARI-19049_trunk.patch > > > Alerts Popup displays full error stacktrace instead of minimal content > STR: > Navigate to any service page > Click on Alerts button from top right corner of summary panel > The complete error message should be displayed as a tooltip text or minimal > text should be displayed. But the complete stacktrace is displayed in the > popup window which makes the list of alerts look unorganized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19068: -- Priority: Critical (was: Major) > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19068: -- Status: Patch Available (was: Open) Verified on the manual cluster that the patch fixes the issue. unit tests are not needed for this patch as fix is only changing the default value for a property (metadata change) > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-19068: -- Attachment: AMBARI-19068.patch > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19068.patch > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19068) Logsearch has a 'required' property while adding Ranger which quickly goes off upon navigating to the tab
[ https://issues.apache.org/jira/browse/AMBARI-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reassigned AMBARI-19068: - Assignee: Jaimin Jetly > Logsearch has a 'required' property while adding Ranger which quickly goes > off upon navigating to the tab > - > > Key: AMBARI-19068 > URL: https://issues.apache.org/jira/browse/AMBARI-19068 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > > Navigate to Add service wizard to Add Ranger > At Customize Services Page notcie that Logsearch has a required property > (which is not expected) > Navigate to Logsearch tab to check > Error for required property quickly goes off -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents
[ https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716225#comment-15716225 ] Hudson commented on AMBARI-19018: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #443 (See [https://builds.apache.org/job/Ambari-branch-2.5/443/]) AMBARI-19018 - Services should be able to specify their own resources (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2273639ee6651ad7ba746471a511c768822e4c1]) * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/test/resources/stacks/HDP/0.1/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml * (edit) ambari-server/src/test/python/TestMpacks.py * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py * (add) ambari-server/src/test/resources/dashboards/README.txt * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ComponentInfo.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java > Services should be able to specify their own resources subdirs for sync'ing > to agents > - > > Key: AMBARI-19018 > URL: https://issues.apache.org/jira/browse/AMBARI-19018 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19018.patch > > > A component should be able to specify a custom folder to sync to the agents > in the metainfo.xml. > For example: > > METRICS_GRAFANA > Grafana > MASTER > dashboards > > scripts/metrics_grafana.py > This will sync the resources/dashboards directory to the agents if the > directory exists on the server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Status: Patch Available (was: Open) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Attachment: rb53747.patch > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Status: Open (was: Patch Available) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Attachment: (was: rb53747.patch) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duc Anh Le updated AMBARI-19020: Resolution: Fixed Status: Resolved (was: Patch Available) > Ubuntu14/16 Add Support for Zookeeper on HDP 2.5 > > > Key: AMBARI-19020 > URL: https://issues.apache.org/jira/browse/AMBARI-19020 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.5.0 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 2.4.0, 2.5.0 > > Attachments: AMBARI-19020.patch, AMBARI-19020_1.patch > > > Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks > rolling upgrade on those OSes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19020) Ubuntu14/16 Add Support for Zookeeper on HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15716003#comment-15716003 ] Hudson commented on AMBARI-19020: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6143 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6143/]) AMBARI-19020. Ubuntu14/16 Add Support for Zookeeper on HDP 2.5 (Duc Le (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=05fe42351131f77a6ee5d58da355b1c461562046]) * (edit) ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.6/metainfo.xml > Ubuntu14/16 Add Support for Zookeeper on HDP 2.5 > > > Key: AMBARI-19020 > URL: https://issues.apache.org/jira/browse/AMBARI-19020 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.5.0 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 2.4.0, 2.5.0 > > Attachments: AMBARI-19020.patch, AMBARI-19020_1.patch > > > Zookeeper on HDP 2.5 is not configured to support Ubuntu 14/16, which breaks > rolling upgrade on those OSes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19067) Special characters break creating user homes
Laszlo Puskas created AMBARI-19067: -- Summary: Special characters break creating user homes Key: AMBARI-19067 URL: https://issues.apache.org/jira/browse/AMBARI-19067 Project: Ambari Issue Type: Bug Reporter: Laszlo Puskas Assignee: Laszlo Puskas The initial implementation of the post user creation script generates a json from the csv passed to it to create user home folders in bulk. If usernames contain special characters like quotes etc .. the generated json input file gets broken. The fix is to escape usernames while generating the json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Status: Patch Available (was: Reopened) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Attachment: (was: rb53747.patch) > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-1: --- Attachment: rb53747.patch > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content
[ https://issues.apache.org/jira/browse/AMBARI-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715926#comment-15715926 ] Hudson commented on AMBARI-19049: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6142 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6142/]) AMBARI-19049. Alerts Popup displays full error stacktrace instead of (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=def3b0ae85b968c7dd41307f4c671bf07d4fc826]) * (edit) ambari-web/app/controllers/main/service/info/summary.js * (edit) ambari-web/app/templates/main/service/info/service_alert_popup.hbs > Alerts Popup displays full error stacktrace instead of minimal content > -- > > Key: AMBARI-19049 > URL: https://issues.apache.org/jira/browse/AMBARI-19049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-19049.patch, AMBARI-19049_trunk.patch > > > Alerts Popup displays full error stacktrace instead of minimal content > STR: > Navigate to any service page > Click on Alerts button from top right corner of summary panel > The complete error message should be displayed as a tooltip text or minimal > text should be displayed. But the complete stacktrace is displayed in the > popup window which makes the list of alerts look unorganized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19063) Do not change timeline.metrics.service.webapp.address in move wizard
[ https://issues.apache.org/jira/browse/AMBARI-19063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19063: - Resolution: Fixed Status: Resolved (was: Patch Available) > Do not change timeline.metrics.service.webapp.address in move wizard > > > Key: AMBARI-19063 > URL: https://issues.apache.org/jira/browse/AMBARI-19063 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19063.patch, AMBARI-19063_branch-2.5.patch > > > Do not change timeline.metrics.service.webapp.address when moving Metrics > Collector via Move Wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19064) Refactor widgets on Dashboard page
[ https://issues.apache.org/jira/browse/AMBARI-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715828#comment-15715828 ] Hudson commented on AMBARI-19064: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6141 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6141/]) AMBARI-19064 Refactor widgets on Dashboard page. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9348725b1067fab38907c8eebc172978729394ad]) * (edit) ambari-web/app/views/main/dashboard/widgets/namenode_uptime.js * (edit) ambari-web/test/views/main/dashboard/widgets/hbase_regions_in_transition_test.js * (edit) ambari-web/app/views/main/dashboard/widgets/node_managers_live.js * (edit) ambari-web/app/views/main/dashboard/widgets/hbase_links.js * (edit) ambari-web/app/views/main/dashboard/widgets/namenode_heap.js * (edit) ambari-web/app/views/main/dashboard/widgets/resource_manager_heap.js * (edit) ambari-web/test/views/main/dashboard/widgets/hbase_average_load_test.js * (edit) ambari-web/app/templates/main/dashboard/plus_button_filter.hbs * (edit) ambari-web/test/views/main/dashboard/widgets/uptime_text_widget_test.js * (edit) ambari-web/app/templates/main/dashboard/widgets.hbs * (edit) ambari-web/app/templates/main/dashboard/edit_widget_popup.hbs * (edit) ambari-web/app/views/common/not-scrollable-textarea.js * (edit) ambari-web/app/views/main/dashboard/widgets/flume_agent_live.js * (edit) ambari-web/app/views/main/dashboard/widgets/hbase_master_heap.js * (edit) ambari-web/test/views/main/dashboard/widgets_test.js * (edit) ambari-web/app/views/main/dashboard/widgets/yarn_memory.js * (edit) ambari-web/app/views/main/dashboard/widgets/yarn_links.js * (edit) ambari-web/test/views/main/dashboard/widgets/namenode_rpc_test.js * (edit) ambari-web/app/templates/main/dashboard/widgets/pie_chart.hbs * (edit) ambari-web/test/views/main/dashboard/widget_test.js * (edit) ambari-web/app/views/main/dashboard/widget.js * (edit) ambari-web/app/views/main/dashboard/widgets/uptime_text_widget.js * (edit) ambari-web/app/templates/main/dashboard/edit_widget_popup_single_threshold.hbs * (edit) ambari-web/test/views/main/dashboard/widgets/text_widget_single_threshold_test.js * (edit) ambari-web/app/views/main/dashboard/widgets.js * (edit) ambari-web/app/views/main/dashboard/widgets/metrics_cpu.js * (edit) ambari-web/app/views/main/dashboard/widgets/namenode_rpc.js * (edit) ambari-web/app/views/main/dashboard/widgets/resource_manager_uptime.js * (edit) ambari-web/test/views/main/dashboard/widgets/text_widget_test.js * (edit) ambari-web/app/views/main/dashboard/widgets/text_widget.js * (edit) ambari-web/app/views/main/dashboard/widgets/hawqsegment_live.js * (edit) ambari-web/app/views/main/dashboard/widgets/metrics_load.js * (edit) ambari-web/app/views/main/dashboard/widgets/hdfs_capacity.js * (edit) ambari-web/app/views/main/dashboard/widgets/hbase_regions_in_transition.js * (edit) ambari-web/app/views/main/dashboard/widgets/namenode_cpu.js * (edit) ambari-web/app/views/main/dashboard/widgets/hbase_average_load.js * (edit) ambari-web/app/views/main/dashboard/widgets/metrics_network.js * (edit) ambari-web/app/views/main/dashboard/widgets/pxf_live.js * (edit) ambari-web/app/views/main/dashboard/widgets/supervisor_live.js * (edit) ambari-web/app/mixins/main/dashboard/widgets/editable.js * (edit) ambari-web/app/views/main/dashboard/widgets/hdfs_links.js * (edit) ambari-web/app/views/main/dashboard/widgets/metrics_memory.js * (edit) ambari-web/app/views/main/dashboard/widgets/text_widget_single_threshold.js * (edit) ambari-web/app/views/main/dashboard/widgets/pie_chart_widget.js * (edit) ambari-web/app/views/main/dashboard/widgets/datanode_live.js * (edit) ambari-web/app/views/main/dashboard/widgets/hbase_master_uptime.js > Refactor widgets on Dashboard page > -- > > Key: AMBARI-19064 > URL: https://issues.apache.org/jira/browse/AMBARI-19064 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19064.patch > > > Refactor widgets on Dashboard page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19064) Refactor widgets on Dashboard page
[ https://issues.apache.org/jira/browse/AMBARI-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715743#comment-15715743 ] Andrii Tkach commented on AMBARI-19064: --- committed to trunk > Refactor widgets on Dashboard page > -- > > Key: AMBARI-19064 > URL: https://issues.apache.org/jira/browse/AMBARI-19064 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19064.patch > > > Refactor widgets on Dashboard page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19064) Refactor widgets on Dashboard page
[ https://issues.apache.org/jira/browse/AMBARI-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19064: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Refactor widgets on Dashboard page > -- > > Key: AMBARI-19064 > URL: https://issues.apache.org/jira/browse/AMBARI-19064 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19064.patch > > > Refactor widgets on Dashboard page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
[
https://issues.apache.org/jira/browse/AMBARI-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715705#comment-15715705
]
Hadoop QA commented on AMBARI-19055:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841491/AMBARI-19055.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/9509//console
This message is automatically generated.
> Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
>
>
> Key: AMBARI-19055
> URL: https://issues.apache.org/jira/browse/AMBARI-19055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19055.patch
>
>
> It may be necessary to remove entries from the {{host_role_command}} table if
> the size of the table has grown excessively large in order to reduce the
> query times for "IN_PROGRESS" requests.
> However, if you remove all tasks for an upgrade, but you leave the stages,
> request, and upgrade items, the upgrade will appear as though it is now
> {{PENDING}}.
> {noformat:title=Before Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "COMPLETED",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> {noformat:title=After Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "PENDING",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> The actual request is showing as {{COMPLETED}} correctly:
> {noformat}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/requests/12;,
> "Requests": {
> "aborted_task_count": 0,
> "cluster_name": "c1",
> "completed_task_count": 0,
> "create_time": 1480517560897,
> "end_time": 1480517643350,
> "exclusive": false,
> "failed_task_count": 0,
> "id": 12,
> "inputs": null,
> "operation_level": null,
> "progress_percent": 100,
> "queued_task_count": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_schedule": null,
> "request_status": "COMPLETED",
> "resource_filters": [],
> "start_time": 1480517560950,
> "task_count": 0,
> "timed_out_task_count": 0,
> "type": "INTERNAL_REQUEST"
> },
> "tasks": [],
> ...
> {noformat}
> STR:
> - Perform a simple upgrade of a ZK-only cluster
> - Find out the ID of the upgrade request (say its 12)
> - Remove tasks
> {code}
> DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
> host_role_command WHERE request_id = 12)
> DELETE FROM host_role_command WHERE request_id = 12
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19064) Refactor widgets on Dashboard page
[
https://issues.apache.org/jira/browse/AMBARI-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715698#comment-15715698
]
Hadoop QA commented on AMBARI-19064:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841492/AMBARI-19064.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 8 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9508//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9508//console
This message is automatically generated.
> Refactor widgets on Dashboard page
> --
>
> Key: AMBARI-19064
> URL: https://issues.apache.org/jira/browse/AMBARI-19064
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-19064.patch
>
>
> Refactor widgets on Dashboard page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19066) Add more logging around status command report processing on server side
Sandor Magyari created AMBARI-19066: --- Summary: Add more logging around status command report processing on server side Key: AMBARI-19066 URL: https://issues.apache.org/jira/browse/AMBARI-19066 Project: Ambari Issue Type: New Feature Components: ambari-server Reporter: Sandor Magyari Assignee: Sandor Magyari Add more INFO level logging in HeartbeatProcessor.processStatusReports, AgentRequests.setExecutionDetailsRequest to be able to trace status command report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[
https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715634#comment-15715634
]
Hadoop QA commented on AMBARI-18926:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841464/AMBARI-18926-3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9507//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9507//console
This message is automatically generated.
> Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
> --
>
> Key: AMBARI-18926
> URL: https://issues.apache.org/jira/browse/AMBARI-18926
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk, 2.4.0
>Reporter: Jesus Alvarez
>Assignee: Jesus Alvarez
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png
>
>
> If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the
> kerberos wizard will create duplicate radio buttons if a user navigates Back
> from step2 to step1 of the kerberos wizard.
> Issue here that in step1_controller.js, options.pushObject(ipaOption) will be
> called on every loadStep.. including when navigating back to step1 from a
> later step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19053) RU: wrong version exposed when Downgrade is going
[
https://issues.apache.org/jira/browse/AMBARI-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715632#comment-15715632
]
Hudson commented on AMBARI-19053:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6140 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6140/])
AMBARI-19053. RU: wrong version exposed when Downgrade is going (ncole) (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7eb2eaa73315189533e039b45cf90655adf25390])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
> RU: wrong version exposed when Downgrade is going
> -
>
> Key: AMBARI-19053
> URL: https://issues.apache.org/jira/browse/AMBARI-19053
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19053.patch
>
>
> Currently on downgrade server returns from and to version same:
> {code:java}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/upgrades/7?fields=Upgrade/*&_=1479742056069;,
> "Upgrade" : {
> "cluster_name" : "c1",
> "create_time" : 1479741414972,
> "direction" : "DOWNGRADE",
> "downgrade_allowed" : true,
> "end_time" : -1,
> "exclusive" : false,
> "from_version" : "2.3.6.0-3796",
> "pack" : "nonrolling-upgrade-2.4",
> "progress_percent" : 56.664,
> "request_context" : "Downgrading to 2.3.6.0-3796",
> "request_id" : 7,
> "request_status" : "HOLDING_TIMEDOUT",
> "skip_failures" : false,
> "skip_service_check_failures" : false,
> "start_time" : 1479741415378,
> "suspended" : false,
> "to_version" : "2.3.6.0-3796",
> "type" : "INTERNAL_REQUEST",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> {code}
> However they should be:
> ||Direction||from_version||to_version||
> |UPGRADE|2.5.0.0|2.5.1.0|
> |DOWNGRADE|2.5.1.0|2.5.0.0|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents
[ https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715630#comment-15715630 ] Hudson commented on AMBARI-19018: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6140 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6140/]) AMBARI-19018 - Services should be able to specify their own resources (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=232a9d87e72dfb87e0d25f6a4cba6738e27beb53]) * (edit) ambari-server/src/test/resources/stacks/HDP/0.1/services/HDFS/metainfo.xml * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py * (edit) ambari-server/src/test/python/TestMpacks.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java * (add) ambari-server/src/test/resources/dashboards/README.txt * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ComponentInfo.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py > Services should be able to specify their own resources subdirs for sync'ing > to agents > - > > Key: AMBARI-19018 > URL: https://issues.apache.org/jira/browse/AMBARI-19018 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19018.patch > > > A component should be able to specify a custom folder to sync to the agents > in the metainfo.xml. > For example: > > METRICS_GRAFANA > Grafana > MASTER > dashboards > > scripts/metrics_grafana.py > This will sync the resources/dashboards directory to the agents if the > directory exists on the server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715625#comment-15715625 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6140 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6140/]) Revert "AMBARI-1: Ambari-agent: Create configuration files with (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=60a6bd4575fb87fc26c4a277cbabf850ef2089e1]) * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-agent/src/packages/tarball/all.xml > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715602#comment-15715602 ] Hudson commented on AMBARI-1: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #442 (See [https://builds.apache.org/job/Ambari-branch-2.5/442/]) Revert "AMBARI-1: Ambari-agent: Create configuration files with (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5c67068d6a29e2ab09591c73a5dca4ac2ae2f622]) * (edit) ambari-agent/conf/unix/ambari-agent.ini * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java > Ambari-agent: Create configuration files with JCEKS information > --- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Attachments: rb53747.patch > > > When a non-status command is received, a command.json file is generated. This > file contains the passwords used in a configuration. When the command is then > executed, ambari agent spawns off a subprocess to execute component-specific > Python scripts to generate the configuration files using the data from the > command.json file. > To avoid storing clear text passwords in command.json file and configuration > files, ambari-agent will first generate the JCEKS files corresponding to the > configuration information in the command JSON blob coming from the server and > then generate the command.json with the path to the JCEKS store instead of > clear text passwords for *password* properties. > Subsequently when executing a command, ambari-agent will generate the > configuration files with the JCEKS path information from command.json. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19062) Hive view history tab does not list queries, if there are large number of queries
[
https://issues.apache.org/jira/browse/AMBARI-19062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715568#comment-15715568
]
Hadoop QA commented on AMBARI-19062:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841468/AMBARI-19062_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9506//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9506//console
This message is automatically generated.
> Hive view history tab does not list queries, if there are large number of
> queries
> -
>
> Key: AMBARI-19062
> URL: https://issues.apache.org/jira/browse/AMBARI-19062
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-19062_branch-2.5.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"
[ https://issues.apache.org/jira/browse/AMBARI-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715571#comment-15715571 ] Dmytro Sen commented on AMBARI-19032: - Committed additional patch to branch-2.5 > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'" > - > > Key: AMBARI-19032 > URL: https://issues.apache.org/jira/browse/AMBARI-19032 > Project: Ambari > Issue Type: Bug > Components: alerts, ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch, > AMBARI-19032_branch2.5_additional.patch > > > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'". > STR: > Update the alert definition interval to 1 min, and thresholds to have minimum > values to trigger the Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19065) Ambari Metrics - Grafana should include the resources/dashboards directory to sync to agents
[ https://issues.apache.org/jira/browse/AMBARI-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe resolved AMBARI-19065. - Resolution: Implemented This was already implemented in AMBARI-19018. > Ambari Metrics - Grafana should include the resources/dashboards directory to > sync to agents > > > Key: AMBARI-19065 > URL: https://issues.apache.org/jira/browse/AMBARI-19065 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"
[ https://issues.apache.org/jira/browse/AMBARI-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715552#comment-15715552 ] Aravindan Vijayan commented on AMBARI-19032: +1 for additional patch. > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'" > - > > Key: AMBARI-19032 > URL: https://issues.apache.org/jira/browse/AMBARI-19032 > Project: Ambari > Issue Type: Bug > Components: alerts, ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch, > AMBARI-19032_branch2.5_additional.patch > > > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'". > STR: > Update the alert definition interval to 1 min, and thresholds to have minimum > values to trigger the Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19065) Ambari Metrics - Grafana should include the resources/dashboards directory to sync to agents
Tim Thorpe created AMBARI-19065: --- Summary: Ambari Metrics - Grafana should include the resources/dashboards directory to sync to agents Key: AMBARI-19065 URL: https://issues.apache.org/jira/browse/AMBARI-19065 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Tim Thorpe Assignee: Tim Thorpe Fix For: trunk, 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19018) Services should be able to specify their own resources subdirs for sync'ing to agents
[ https://issues.apache.org/jira/browse/AMBARI-19018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19018: Resolution: Fixed Status: Resolved (was: Patch Available) > Services should be able to specify their own resources subdirs for sync'ing > to agents > - > > Key: AMBARI-19018 > URL: https://issues.apache.org/jira/browse/AMBARI-19018 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19018.patch > > > A component should be able to specify a custom folder to sync to the agents > in the metainfo.xml. > For example: > > METRICS_GRAFANA > Grafana > MASTER > dashboards > > scripts/metrics_grafana.py > This will sync the resources/dashboards directory to the agents if the > directory exists on the server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19053) RU: wrong version exposed when Downgrade is going
[
https://issues.apache.org/jira/browse/AMBARI-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-19053:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> RU: wrong version exposed when Downgrade is going
> -
>
> Key: AMBARI-19053
> URL: https://issues.apache.org/jira/browse/AMBARI-19053
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19053.patch
>
>
> Currently on downgrade server returns from and to version same:
> {code:java}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/upgrades/7?fields=Upgrade/*&_=1479742056069;,
> "Upgrade" : {
> "cluster_name" : "c1",
> "create_time" : 1479741414972,
> "direction" : "DOWNGRADE",
> "downgrade_allowed" : true,
> "end_time" : -1,
> "exclusive" : false,
> "from_version" : "2.3.6.0-3796",
> "pack" : "nonrolling-upgrade-2.4",
> "progress_percent" : 56.664,
> "request_context" : "Downgrading to 2.3.6.0-3796",
> "request_id" : 7,
> "request_status" : "HOLDING_TIMEDOUT",
> "skip_failures" : false,
> "skip_service_check_failures" : false,
> "start_time" : 1479741415378,
> "suspended" : false,
> "to_version" : "2.3.6.0-3796",
> "type" : "INTERNAL_REQUEST",
> "upgrade_type" : "NON_ROLLING"
> }
> }
> {code}
> However they should be:
> ||Direction||from_version||to_version||
> |UPGRADE|2.5.0.0|2.5.1.0|
> |DOWNGRADE|2.5.1.0|2.5.0.0|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19055) Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
[
https://issues.apache.org/jira/browse/AMBARI-19055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715538#comment-15715538
]
Hudson commented on AMBARI-19055:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6139 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6139/])
AMBARI-19055 - Removing Tasks From host_role_command Causes Upgrades To
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=32840c1ed434ae4cc99e3ab6f7d3f2604fb69d06])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CalculatedStatusTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
> Removing Tasks From host_role_command Causes Upgrades To Show As PENDING
>
>
> Key: AMBARI-19055
> URL: https://issues.apache.org/jira/browse/AMBARI-19055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19055.patch
>
>
> It may be necessary to remove entries from the {{host_role_command}} table if
> the size of the table has grown excessively large in order to reduce the
> query times for "IN_PROGRESS" requests.
> However, if you remove all tasks for an upgrade, but you leave the stages,
> request, and upgrade items, the upgrade will appear as though it is now
> {{PENDING}}.
> {noformat:title=Before Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "COMPLETED",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> {noformat:title=After Removal}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12;,
> "Upgrade": {
> "cluster_name": "c1",
> "create_time": 1480517560897,
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "end_time": 1480517643350,
> "exclusive": false,
> "from_version": "2.5.0.0-1237",
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_id": 12,
> "request_status": "PENDING",
> "skip_failures": false,
> "skip_service_check_failures": false,
> "start_time": 1480517560950,
> "suspended": false,
> "to_version": "2.5.2.0-67",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING"
> },
> "upgrade_groups": [
> ...
> {noformat}
> The actual request is showing as {{COMPLETED}} correctly:
> {noformat}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/requests/12;,
> "Requests": {
> "aborted_task_count": 0,
> "cluster_name": "c1",
> "completed_task_count": 0,
> "create_time": 1480517560897,
> "end_time": 1480517643350,
> "exclusive": false,
> "failed_task_count": 0,
> "id": 12,
> "inputs": null,
> "operation_level": null,
> "progress_percent": 100,
> "queued_task_count": 0,
> "request_context": "Upgrading to 2.5.2.0-67",
> "request_schedule": null,
> "request_status": "COMPLETED",
> "resource_filters": [],
> "start_time": 1480517560950,
> "task_count": 0,
> "timed_out_task_count": 0,
> "type": "INTERNAL_REQUEST"
> },
> "tasks": [],
> ...
> {noformat}
> STR:
> - Perform a simple upgrade of a ZK-only cluster
> - Find out the ID of the upgrade request (say its 12)
> - Remove tasks
> {code}
> DELETE FROM execution_command WHERE task_id IN (SELECT task_id FROM
> host_role_command WHERE request_id = 12)
> DELETE FROM host_role_command WHERE request_id = 12
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715533#comment-15715533 ] Hudson commented on AMBARI-18944: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6139 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6139/]) AMBARI-18944 - Improve remoteIp in audit log (Wang Yaoxin via (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f4ea309196a2c02b88f5e5ce062200d50d888005]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/utils/RequestUtilsTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/utils/RequestUtils.java > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch, > AMBARI-18944_02.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715534#comment-15715534 ] Hudson commented on AMBARI-18441: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6139 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6139/]) AMBARI-18441 - upgrade ambari to 2.1.1 error (Wang Yaoxin via (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ae3ff2a09b6b36f8a456987c60fc695dd262b6bb]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog211.java > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18411-03.patch, AMBARI-18441-01.patch, > AMBARI-18441-02.patch, AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19032) HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has no attribute 'split'"
[ https://issues.apache.org/jira/browse/AMBARI-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-19032: Attachment: AMBARI-19032_branch2.5_additional.patch > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'" > - > > Key: AMBARI-19032 > URL: https://issues.apache.org/jira/browse/AMBARI-19032 > Project: Ambari > Issue Type: Bug > Components: alerts, ambari-metrics >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19032_1.patch, AMBARI-19032_2.patch, > AMBARI-19032_branch2.5_additional.patch > > > HDFS Metric alerts turns to UNKNOWN state with error "'NoneType' object has > no attribute 'split'". > STR: > Update the alert definition interval to 1 min, and thresholds to have minimum > values to trigger the Alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715522#comment-15715522
]
Hadoop QA commented on AMBARI-19007:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841476/AMBARI-19007-trunk.02.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 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9505//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9505//console
This message is automatically generated.
> Atlas to support configuration of hooks from separate cluster
> -
>
> Key: AMBARI-19007
> URL: https://issues.apache.org/jira/browse/AMBARI-19007
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19007-trunk.01.patch,
> AMBARI-19007-trunk.02.patch, AMBARI-19007-trunk.patch, AMBARI-19007.01.patch,
> AMBARI-19007.02.patch, AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715509#comment-15715509 ] Hudson commented on AMBARI-18944: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #441 (See [https://builds.apache.org/job/Ambari-branch-2.5/441/]) AMBARI-18944 - Improve remoteIp in audit log (Wang Yaoxin via (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8039a1f6e346f01505cf1e9d508fb6b7676cb09e]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/utils/RequestUtils.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/utils/RequestUtilsTest.java > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch, > AMBARI-18944_02.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715511#comment-15715511 ] Hudson commented on AMBARI-18441: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #441 (See [https://builds.apache.org/job/Ambari-branch-2.5/441/]) AMBARI-18441 - upgrade ambari to 2.1.1 error (Wang Yaoxin via (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0a58f91645f58f71ce729a71a5a821f24514e116]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog211.java > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18411-03.patch, AMBARI-18441-01.patch, > AMBARI-18441-02.patch, AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
[
https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley reopened AMBARI-1:
--
Reverting this from trunk/branch-2.5 because it's causing agent heartbeats to
fail on commands executed before a cluster is created:
{code}
02 Dec 2016 15:30:55,079 WARN [qtp-ambari-agent-42] AgentResource:136 - Error
in HeartBeat
org.apache.ambari.server.ClusterNotFoundException: Cluster not found,
clusterName=null
at
org.apache.ambari.server.state.cluster.ClustersImpl.getCluster(ClustersImpl.java:277)
at
org.apache.ambari.server.agent.HeartBeatHandler.sendCommands(HeartBeatHandler.java:335)
at
org.apache.ambari.server.agent.HeartBeatHandler.handleHeartBeat(HeartBeatHandler.java:298)
at
org.apache.ambari.server.agent.rest.AgentResource.heartbeat(AgentResource.java:130)
at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
{code}
> Ambari-agent: Create configuration files with JCEKS information
> ---
>
> Key: AMBARI-1
> URL: https://issues.apache.org/jira/browse/AMBARI-1
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Attachments: rb53747.patch
>
>
> When a non-status command is received, a command.json file is generated. This
> file contains the passwords used in a configuration. When the command is then
> executed, ambari agent spawns off a subprocess to execute component-specific
> Python scripts to generate the configuration files using the data from the
> command.json file.
> To avoid storing clear text passwords in command.json file and configuration
> files, ambari-agent will first generate the JCEKS files corresponding to the
> configuration information in the command JSON blob coming from the server and
> then generate the command.json with the path to the JCEKS store instead of
> clear text passwords for *password* properties.
> Subsequently when executing a command, ambari-agent will generate the
> configuration files with the JCEKS path information from command.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18951) Force InnoDB usage for MySQL
[ https://issues.apache.org/jira/browse/AMBARI-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715454#comment-15715454 ] Hudson commented on AMBARI-18951: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6138 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6138/]) AMBARI-18951. Force InnoDB usage for MySQL. Fix for MySQL < 5.6. (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=80084a9d8de9110365c6f1ef68362b502e07cf28]) * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql > Force InnoDB usage for MySQL > > > Key: AMBARI-18951 > URL: https://issues.apache.org/jira/browse/AMBARI-18951 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18951.patch > > > We should always use InnoDB as database engine for MySQL as database with > MyISAM engine cannot be upgraded properly. > Key reason is that MyISAM doesn't store foreign keys information, but do > store indexes with same name which lead to conflicts during upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18951) Force InnoDB usage for MySQL
[ https://issues.apache.org/jira/browse/AMBARI-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715428#comment-15715428 ] Hudson commented on AMBARI-18951: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #440 (See [https://builds.apache.org/job/Ambari-branch-2.5/440/]) AMBARI-18951. Force InnoDB usage for MySQL. Fix for MySQL < 5.6. (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=171279a25cf12cd1f3c13ee70e366ca0f5f4a53f]) * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql > Force InnoDB usage for MySQL > > > Key: AMBARI-18951 > URL: https://issues.apache.org/jira/browse/AMBARI-18951 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18951.patch > > > We should always use InnoDB as database engine for MySQL as database with > MyISAM engine cannot be upgraded properly. > Key reason is that MyISAM doesn't store foreign keys information, but do > store indexes with same name which lead to conflicts during upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19049) Alerts Popup displays full error stacktrace instead of minimal content
[
https://issues.apache.org/jira/browse/AMBARI-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715424#comment-15715424
]
Hadoop QA commented on AMBARI-19049:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841482/AMBARI-19049_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9504//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9504//console
This message is automatically generated.
> Alerts Popup displays full error stacktrace instead of minimal content
> --
>
> Key: AMBARI-19049
> URL: https://issues.apache.org/jira/browse/AMBARI-19049
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19049.patch, AMBARI-19049_trunk.patch
>
>
> Alerts Popup displays full error stacktrace instead of minimal content
> STR:
> Navigate to any service page
> Click on Alerts button from top right corner of summary panel
> The complete error message should be displayed as a tooltip text or minimal
> text should be displayed. But the complete stacktrace is displayed in the
> popup window which makes the list of alerts look unorganized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[
https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18944:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to {{trunk}} and {{branch-2.5}}
> Improve remoteIp in audit log
> -
>
> Key: AMBARI-18944
> URL: https://issues.apache.org/jira/browse/AMBARI-18944
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch,
> AMBARI-18944_02.patch
>
>
> Mutil-agent were configured in some production environments, RemoteIp
> therefore will obtain mutilple IP addresses, like
> (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
