[jira] [Updated] (AMBARI-26074) Upgrade logback core and logback classic to 1.2.13
[ https://issues.apache.org/jira/browse/AMBARI-26074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26074: - Fix Version/s: 3.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade logback core and logback classic to 1.2.13 > -- > > Key: AMBARI-26074 > URL: https://issues.apache.org/jira/browse/AMBARI-26074 > Project: Ambari > Issue Type: Improvement >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade logback core and logback classic to 1.2.13 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-26034) Remove ambari-logsearch and ambari-infra from default build profiles
[ https://issues.apache.org/jira/browse/AMBARI-26034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-26034. -- Resolution: Won't Fix > Remove ambari-logsearch and ambari-infra from default build profiles > > > Key: AMBARI-26034 > URL: https://issues.apache.org/jira/browse/AMBARI-26034 > Project: Ambari > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > ambari-logsearch and ambari-infra are not maintained from long time. > Also these projects are moved to following sub projects and have separate git > repository. > https://github.com/apache/ambari-logsearch > https://github.com/apache/ambari-infra > Can not remove these codes from branch-2.7 at this point in time and I think > it is ok to not build these projects by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-26000) Ambari supports Python3 environment
[
https://issues.apache.org/jira/browse/AMBARI-26000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad resolved AMBARI-26000.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Ambari supports Python3 environment
> ---
>
> Key: AMBARI-26000
> URL: https://issues.apache.org/jira/browse/AMBARI-26000
> Project: Ambari
> Issue Type: New Feature
>Reporter: wenweijian
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Ambari support python3.md
>
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> This patch is about upgrade python3 on trunk branch.
> All unit tests are passed on python3 version.
> We also deploy it in the production environment(Centos7) and it works fine.
> h1. Upgrade Instructions:
> All major changes related to this upgrade are documented in the MD file of
> this issue. Colleagues who need to review and understand the upgrade changes
> can download and review it.
> 1. Required Dependencies:
> After upgrading to Python 3, Ambari requires the 'distro' dependency. To
> install it, run:
> {code:java}
> pip3 install distro {code}
> If you are using CentOS 7, manually install the following dependencies:
> {code:java}
> yum install python3 python3-libs python36-distro python36-rpm {code}
> 2. Compilation and Testing:
> To compile and package, use the following Maven command:
> {code:java}
> mvn -B clean install package rpm:rpm -Dbuild-rpm -Drat.skip=true -DskipTests
> -Dmaven.test.skip=true {code}
> To run unit tests for Ambari server, use:
> {code:java}
> mvn -am test -pl ambari-server -DskipSurefireTests
> -Dmaven.test.failure.ignore -Dmaven.artifact.threads=10 -Drat.skip
> -Dcheckstyle.skip {code}
> To run unit tests for Ambari agent, use:
> {code:java}
> mvn -am test -pl ambari-agent -DskipSurefireTests -Dmaven.test.failure.ignore
> -Dmaven.artifact.threads=10 -Drat.skip -Dcheckstyle.skip{code}
> Note: Before compiling, ensure that you create a symbolic link from
> 'python3' to 'python':
> {code:java}
> rm -f /usr/bin/python
> ln -s /usr/bin/python-3.x /usr/bin/python{code}
> This is necessary because the rpm-maven-plugin used by Ambari for RPM
> packaging defaults to using Python 2, and it cannot be configured to use
> Python 3. This symbolic link change may affect the use of 'yum.' To address
> this, modify the first line in the following files on CentOS 7:
> {code:java}
> /usr/libexec/urlgrabber-ext-down
> /usr/bin/yum
> Change '#!/usr/bin/python' to '#!/usr/bin/python2'{code}
> 3. Testing:
> All unit tests have passed, and we have tested manual installation and
> blueprint testing in the production environment, including common component
> operations.
> 4. How to Test Installation:
> Currently, the trunk supports testing installation on CentOS 7.
> Pre-install the Python 3 dependencies on CentOS 7:
> {code:java}
> yum install python3 python3-libs python36-distro python36-rpm{code}
> The installation steps are the same as before.
> Installation Note:
> Ambari trunk defaults to using the Apache Bigtop stack during installation,
> which relies on the {{bigtop-select}} tool. This tool currently defaults to
> Python 2, but we have updated it to Python 3 for testing purposes.
> Below are the Ambari RPMs required for trunk testing. All Big Data component
> RPMs (packaged using Apache Bigtop) are available for CentOS 7 since trunk
> currently only supports CentOS 7. Download links are provided below.
> http://64.69.37.12:8089/
> We plan to support more operating systems after upgrading to Python 3, which
> will make multi-OS support easier.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26000) Ambari supports Python3 environment
[
https://issues.apache.org/jira/browse/AMBARI-26000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815895#comment-17815895
]
Mohammad Arshad commented on AMBARI-26000:
--
Merged to trunk
https://github.com/apache/ambari/commit/5f95ec6c60ef17d65b0ef2b059feb1b9c482aaa4
Thanks [~leo wen], [~jialiang] for working on this issue.
Thanks [~bpatel], [~hmaurya] for verifying changes and suggesting fixes.
> Ambari supports Python3 environment
> ---
>
> Key: AMBARI-26000
> URL: https://issues.apache.org/jira/browse/AMBARI-26000
> Project: Ambari
> Issue Type: New Feature
>Reporter: wenweijian
>Priority: Major
> Attachments: Ambari support python3.md
>
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> This patch is about upgrade python3 on trunk branch.
> All unit tests are passed on python3 version.
> We also deploy it in the production environment(Centos7) and it works fine.
> h1. Upgrade Instructions:
> All major changes related to this upgrade are documented in the MD file of
> this issue. Colleagues who need to review and understand the upgrade changes
> can download and review it.
> 1. Required Dependencies:
> After upgrading to Python 3, Ambari requires the 'distro' dependency. To
> install it, run:
> {code:java}
> pip3 install distro {code}
> If you are using CentOS 7, manually install the following dependencies:
> {code:java}
> yum install python3 python3-libs python36-distro python36-rpm {code}
> 2. Compilation and Testing:
> To compile and package, use the following Maven command:
> {code:java}
> mvn -B clean install package rpm:rpm -Dbuild-rpm -Drat.skip=true -DskipTests
> -Dmaven.test.skip=true {code}
> To run unit tests for Ambari server, use:
> {code:java}
> mvn -am test -pl ambari-server -DskipSurefireTests
> -Dmaven.test.failure.ignore -Dmaven.artifact.threads=10 -Drat.skip
> -Dcheckstyle.skip {code}
> To run unit tests for Ambari agent, use:
> {code:java}
> mvn -am test -pl ambari-agent -DskipSurefireTests -Dmaven.test.failure.ignore
> -Dmaven.artifact.threads=10 -Drat.skip -Dcheckstyle.skip{code}
> Note: Before compiling, ensure that you create a symbolic link from
> 'python3' to 'python':
> {code:java}
> rm -f /usr/bin/python
> ln -s /usr/bin/python-3.x /usr/bin/python{code}
> This is necessary because the rpm-maven-plugin used by Ambari for RPM
> packaging defaults to using Python 2, and it cannot be configured to use
> Python 3. This symbolic link change may affect the use of 'yum.' To address
> this, modify the first line in the following files on CentOS 7:
> {code:java}
> /usr/libexec/urlgrabber-ext-down
> /usr/bin/yum
> Change '#!/usr/bin/python' to '#!/usr/bin/python2'{code}
> 3. Testing:
> All unit tests have passed, and we have tested manual installation and
> blueprint testing in the production environment, including common component
> operations.
> 4. How to Test Installation:
> Currently, the trunk supports testing installation on CentOS 7.
> Pre-install the Python 3 dependencies on CentOS 7:
> {code:java}
> yum install python3 python3-libs python36-distro python36-rpm{code}
> The installation steps are the same as before.
> Installation Note:
> Ambari trunk defaults to using the Apache Bigtop stack during installation,
> which relies on the {{bigtop-select}} tool. This tool currently defaults to
> Python 2, but we have updated it to Python 3 for testing purposes.
> Below are the Ambari RPMs required for trunk testing. All Big Data component
> RPMs (packaged using Apache Bigtop) are available for CentOS 7 since trunk
> currently only supports CentOS 7. Download links are provided below.
> http://64.69.37.12:8089/
> We plan to support more operating systems after upgrading to Python 3, which
> will make multi-OS support easier.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-26047) Update the ambari-2.7.8 docs
[ https://issues.apache.org/jira/browse/AMBARI-26047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-26047. -- Resolution: Resolved > Update the ambari-2.7.8 docs > > > Key: AMBARI-26047 > URL: https://issues.apache.org/jira/browse/AMBARI-26047 > Project: Ambari > Issue Type: Bug > Components: documentation >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26047) Update the ambari-2.7.8 docs
[ https://issues.apache.org/jira/browse/AMBARI-26047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813373#comment-17813373 ] Mohammad Arshad commented on AMBARI-26047: -- Docs are updated with latest release and published to ambari website http://ambari.apache.org https://cwiki.apache.org/confluence/display/AMBARI/Ambari+User+Guides https://github.com/apache/ambari/commit/af54c417bbdb85938194a9440a6210dcea247d45 Committed to trunk and cherry-picked to branch-2.8, branch-2.7 and branch-2.7.8 > Update the ambari-2.7.8 docs > > > Key: AMBARI-26047 > URL: https://issues.apache.org/jira/browse/AMBARI-26047 > Project: Ambari > Issue Type: Bug > Components: documentation >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26047) Update the ambari-2.7.8 docs
Mohammad Arshad created AMBARI-26047: Summary: Update the ambari-2.7.8 docs Key: AMBARI-26047 URL: https://issues.apache.org/jira/browse/AMBARI-26047 Project: Ambari Issue Type: Bug Components: documentation Reporter: Mohammad Arshad Assignee: Mohammad Arshad -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-25950. -- Resolution: Fixed > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 40m > Remaining Estimate: 0h > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812838#comment-17812838 ] Mohammad Arshad commented on AMBARI-25950: -- Created https://issues.apache.org/jira/browse/AMBARI-26046 to fix this issue in branch-2.8 and trunk. Resolving this issue now. Thanks [~dmmkr] for your contribution. > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 40m > Remaining Estimate: 0h > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812837#comment-17812837 ] Mohammad Arshad commented on AMBARI-25956: -- Thanks [~dmmkr], [~satheeshakuthota] for your contribution. > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26046) Fix AMBARI-25950 in branch-2.8 and trunk
Mohammad Arshad created AMBARI-26046: Summary: Fix AMBARI-25950 in branch-2.8 and trunk Key: AMBARI-26046 URL: https://issues.apache.org/jira/browse/AMBARI-26046 Project: Ambari Issue Type: Bug Reporter: Mohammad Arshad Assignee: D M Murali Krishna Reddy https://issues.apache.org/jira/browse/AMBARI-25950 is fixed in branch-2.7 but need to fixed in branch-2.8 and trunk. Created this jira to close https://issues.apache.org/jira/browse/AMBARI-25950 for Ambari 2.7.8 release. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-25956. -- Resolution: Fixed > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812836#comment-17812836 ] Mohammad Arshad commented on AMBARI-25956: -- Created https://issues.apache.org/jira/browse/AMBARI-26045 to fix this issue in branch-2.8 and trunk. Resolving this jira now. > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26045) Fix AMBARI-25956 in branch-2.8 and trunk
Mohammad Arshad created AMBARI-26045: Summary: Fix AMBARI-25956 in branch-2.8 and trunk Key: AMBARI-26045 URL: https://issues.apache.org/jira/browse/AMBARI-26045 Project: Ambari Issue Type: Bug Reporter: Mohammad Arshad Assignee: D M Murali Krishna Reddy https://issues.apache.org/jira/browse/AMBARI-25956 is fixed in branch-2.7. Need to be fixed branch-2.8 and trunk. Created this jira to close https://issues.apache.org/jira/browse/AMBARI-25956 for Ambari 2.7.8 release -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26043) Upgrade jersey 1.x to 2.41 to support jdk 17
[ https://issues.apache.org/jira/browse/AMBARI-26043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26043: - Description: Upgrade jersey 1.x to 2.41 to support jdk 17 (was: Upgrade jersey 1.x to 2.4.1 to support jdk 17) Summary: Upgrade jersey 1.x to 2.41 to support jdk 17 (was: Upgrade jersey 1.x to 2.4.1 to support jdk 17) > Upgrade jersey 1.x to 2.41 to support jdk 17 > > > Key: AMBARI-26043 > URL: https://issues.apache.org/jira/browse/AMBARI-26043 > Project: Ambari > Issue Type: Improvement >Reporter: Mohammad Arshad >Priority: Major > > Upgrade jersey 1.x to 2.41 to support jdk 17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26044) Analyse how to handle power mock to support JDK 18
Mohammad Arshad created AMBARI-26044: Summary: Analyse how to handle power mock to support JDK 18 Key: AMBARI-26044 URL: https://issues.apache.org/jira/browse/AMBARI-26044 Project: Ambari Issue Type: Improvement Reporter: Mohammad Arshad Currently power mock does not support jdk 17. Need to find out workaround or alternate to support jdk 17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26041) Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17
[ https://issues.apache.org/jira/browse/AMBARI-26041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26041: - Epic Link: AMBARI-26040 (was: AMBARI-9784) > Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17 > --- > > Key: AMBARI-26041 > URL: https://issues.apache.org/jira/browse/AMBARI-26041 > Project: Ambari > Issue Type: Improvement >Reporter: Mohammad Arshad >Priority: Major > > Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26040) Support JDK 17 in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-26040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26040: - Epic Name: Support JDK 17 in Ambari (was: JDK17) > Support JDK 17 in Ambari > > > Key: AMBARI-26040 > URL: https://issues.apache.org/jira/browse/AMBARI-26040 > Project: Ambari > Issue Type: Epic >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > > Add JDK17 support in Ambari for improved security, performance improvement > and future security patch availability. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26043) Upgrade jersey 1.x to 2.4.1 to support jdk 17
[ https://issues.apache.org/jira/browse/AMBARI-26043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26043: - Epic Link: AMBARI-26040 > Upgrade jersey 1.x to 2.4.1 to support jdk 17 > - > > Key: AMBARI-26043 > URL: https://issues.apache.org/jira/browse/AMBARI-26043 > Project: Ambari > Issue Type: Improvement >Reporter: Mohammad Arshad >Priority: Major > > Upgrade jersey 1.x to 2.4.1 to support jdk 17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26042) Upgrade eclipselink to 2.7.14 to support JDK 17
[ https://issues.apache.org/jira/browse/AMBARI-26042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26042: - Summary: Upgrade eclipselink to 2.7.14 to support JDK 17 (was: Upgrade eclipselink to 2.7.14 to support jdk17) > Upgrade eclipselink to 2.7.14 to support JDK 17 > > > Key: AMBARI-26042 > URL: https://issues.apache.org/jira/browse/AMBARI-26042 > Project: Ambari > Issue Type: Improvement >Reporter: Mohammad Arshad >Priority: Major > > Upgrade eclipselink to 2.7.14 to support jdk17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26043) Upgrade jersey 1.x to 2.4.1 to support jdk 17
Mohammad Arshad created AMBARI-26043: Summary: Upgrade jersey 1.x to 2.4.1 to support jdk 17 Key: AMBARI-26043 URL: https://issues.apache.org/jira/browse/AMBARI-26043 Project: Ambari Issue Type: Improvement Reporter: Mohammad Arshad Upgrade jersey 1.x to 2.4.1 to support jdk 17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26042) Upgrade eclipselink to 2.7.14 to support jdk17
[ https://issues.apache.org/jira/browse/AMBARI-26042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26042: - Epic Link: AMBARI-9784 > Upgrade eclipselink to 2.7.14 to support jdk17 > -- > > Key: AMBARI-26042 > URL: https://issues.apache.org/jira/browse/AMBARI-26042 > Project: Ambari > Issue Type: Improvement >Reporter: Mohammad Arshad >Priority: Major > > Upgrade eclipselink to 2.7.14 to support jdk17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26042) Upgrade eclipselink to 2.7.14 to support jdk17
Mohammad Arshad created AMBARI-26042: Summary: Upgrade eclipselink to 2.7.14 to support jdk17 Key: AMBARI-26042 URL: https://issues.apache.org/jira/browse/AMBARI-26042 Project: Ambari Issue Type: Improvement Reporter: Mohammad Arshad Upgrade eclipselink to 2.7.14 to support jdk17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26041) Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17
Mohammad Arshad created AMBARI-26041: Summary: Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17 Key: AMBARI-26041 URL: https://issues.apache.org/jira/browse/AMBARI-26041 Project: Ambari Issue Type: Improvement Reporter: Mohammad Arshad Upgrade to juice 5.10 as guice 4.1.0 does not support jdk17 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26040) Support JDK 17 in Ambari
Mohammad Arshad created AMBARI-26040: Summary: Support JDK 17 in Ambari Key: AMBARI-26040 URL: https://issues.apache.org/jira/browse/AMBARI-26040 Project: Ambari Issue Type: Epic Reporter: Mohammad Arshad Assignee: Mohammad Arshad Add JDK17 support in Ambari for improved security, performance improvement and future security patch availability. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26033) Release Ambari 2.7.8
[ https://issues.apache.org/jira/browse/AMBARI-26033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806318#comment-17806318 ] Mohammad Arshad commented on AMBARI-26033: -- None of issues, found so far, are blocking, created release candidate rc0 and shared for voting. > Release Ambari 2.7.8 > > > Key: AMBARI-26033 > URL: https://issues.apache.org/jira/browse/AMBARI-26033 > Project: Ambari > Issue Type: Task >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25950: - Fix Version/s: 2.7.8 > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 40m > Remaining Estimate: 0h > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25956) [ Rolling upgrade] Hive Server Going down after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25956: - Fix Version/s: 2.7.8 > [ Rolling upgrade] Hive Server Going down after upgrade > --- > > Key: AMBARI-25956 > URL: https://issues.apache.org/jira/browse/AMBARI-25956 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: Satheesh Akuthota >Assignee: D M Murali Krishna Reddy >Priority: Major > Fix For: 2.7.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hi Team , > STR : > 1. Install HDP 2.6.5 cluster with Multiple HS2 clients > 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari > Expected Result : All the services should be up and running > Observed Result : one of the HS2 going down -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25725) Upgrade bootstrap.min.js to v5.2.0
[ https://issues.apache.org/jira/browse/AMBARI-25725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25725: - Fix Version/s: 2.7.8 (was: 2.7.7) > Upgrade bootstrap.min.js to v5.2.0 > -- > > Key: AMBARI-25725 > URL: https://issues.apache.org/jira/browse/AMBARI-25725 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Fix For: 2.8.0, 2.7.8 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25849) Need to update org.jboss.netty: netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25849: - Fix Version/s: (was: 2.7.8) > Need to update org.jboss.netty: netty dependency > > > Key: AMBARI-25849 > URL: https://issues.apache.org/jira/browse/AMBARI-25849 > Project: Ambari > Issue Type: Improvement > Components: metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25849.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.jboss.netty: netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25851) Need to update com.fasterxml.jackson.core :jackson-databind dependency
[ https://issues.apache.org/jira/browse/AMBARI-25851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25851: - Fix Version/s: (was: 2.7.8) > Need to update com.fasterxml.jackson.core :jackson-databind dependency > -- > > Key: AMBARI-25851 > URL: https://issues.apache.org/jira/browse/AMBARI-25851 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25851.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to update com.fasterxml.jackson.core :jackson-databind dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25844) Need to update commons-collection dependency
[ https://issues.apache.org/jira/browse/AMBARI-25844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25844: - Fix Version/s: (was: 2.7.8) > Need to update commons-collection dependency > > > Key: AMBARI-25844 > URL: https://issues.apache.org/jira/browse/AMBARI-25844 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25844.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update commons-collection dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25848) Need to update org.codehaus.jackson:jackson-mapper-asl dependency
[ https://issues.apache.org/jira/browse/AMBARI-25848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25848: - Fix Version/s: (was: 2.7.8) > Need to update org.codehaus.jackson:jackson-mapper-asl dependency > - > > Key: AMBARI-25848 > URL: https://issues.apache.org/jira/browse/AMBARI-25848 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-metrics, ambari-server, contrib >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25848.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.codehaus.jackson:jackson-mapper-asl dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25850) Need to update com.h2database:h2 dependency
[ https://issues.apache.org/jira/browse/AMBARI-25850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25850: - Fix Version/s: (was: 2.7.8) > Need to update com.h2database:h2 dependency > --- > > Key: AMBARI-25850 > URL: https://issues.apache.org/jira/browse/AMBARI-25850 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25850.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Need to update com.h2database:h2 dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25845) Need to update io.netty:netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25845: - Fix Version/s: (was: 2.7.8) > Need to update io.netty:netty dependency > > > Key: AMBARI-25845 > URL: https://issues.apache.org/jira/browse/AMBARI-25845 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25845.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update io.netty:netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25847) Need to update log4j:log4j dependency
[ https://issues.apache.org/jira/browse/AMBARI-25847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25847: - Fix Version/s: (was: 2.7.8) > Need to update log4j:log4j dependency > - > > Key: AMBARI-25847 > URL: https://issues.apache.org/jira/browse/AMBARI-25847 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25847.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Need to update log4j:log4j dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25843) Update Zookeeper version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25843: - Fix Version/s: (was: 2.7.8) > Update Zookeeper version in Ambari > -- > > Key: AMBARI-25843 > URL: https://issues.apache.org/jira/browse/AMBARI-25843 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra, ambari-logsearch, ambari-metrics >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25843-branch-2.7.7.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Need to update zookeeper version in Ambari -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25911) Ambari fails to capture Hive Metastore alerts when HMS is critical or goes OOM
[ https://issues.apache.org/jira/browse/AMBARI-25911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25911: - Fix Version/s: (was: 2.7.8) > Ambari fails to capture Hive Metastore alerts when HMS is critical or goes OOM > -- > > Key: AMBARI-25911 > URL: https://issues.apache.org/jira/browse/AMBARI-25911 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > > Ambari fails to capture Hive Metastore alerts when HMS is critical or goes > OOM. Thus rendering the alert check ineffective. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26038) Fix WidgetResourceProviderTest failure
Mohammad Arshad created AMBARI-26038:
Summary: Fix WidgetResourceProviderTest failure
Key: AMBARI-26038
URL: https://issues.apache.org/jira/browse/AMBARI-26038
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
[ERROR] Failures:
[ERROR] WidgetResourceProviderTest.testCreateResources:260
expected:<[[{"name":"value","name2":"value2"}]]> but was:<[[
{
"name": "value",
"name2": "value2"
}
]]>
[ERROR] WidgetResourceProviderTest.testUpdateResources:353
expected:<[[{"name":"new_value","new_name":"new_value2"}]]> but was:<[[
{
"name": "new_value",
"new_name": "new_value2"
}
]]>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26037) ambari-server java test failures
[
https://issues.apache.org/jira/browse/AMBARI-26037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-26037:
-
Description:
{noformat}
mvn -am test -pl ambari-server -DskipPythonTests -Dmaven.test.failure.ignore
-Dmaven.artifact.threads=10 -Drat.skip
{noformat}
{code:java}
[ERROR] Failures:
[ERROR] WidgetResourceProviderTest.testCreateResources:260
expected:<[[{"name":"value","name2":"value2"}]]> but was:<[[
{
"name": "value",
"name2": "value2"
}
]]>
[ERROR] WidgetResourceProviderTest.testUpdateResources:353
expected:<[[{"name":"new_value","new_name":"new_value2"}]]> but was:<[[
{
"name": "new_value",
"new_name": "new_value2"
}
]]>
[ERROR] Errors:
[ERROR] AmbariManagementControllerTest.testCreateActionsFailures:4332 ?
Ambari Action ...
[ERROR]
RootServiceComponentConfigurationResourceProviderTest.shouldUpdatePasswordInCredentialStoreIfSecurityPasswordEncryptionIsEnabled:534
? ConstructorNotFound
[ERROR] DDLTests.testCompareMySQL:134->compareAgainstPostgres:150 ?
UncheckedExecution
[ERROR] DDLTests.testVerifyMySQL:60->verifyDDL:89 ? UncheckedExecution
java.lang.Illeg...
[ERROR]
PasswordUtilsTest.shouldReadPasswordFromCredentialStoreOfAnAlias:67->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[ERROR]
PasswordUtilsTest.shouldResolveEncryptedPaswordIfWeStoreTheAliasInPasswordFile:103->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[INFO]
[ERROR] *Tests run: 5230, Failures: 2, Errors: 6, Skipped: 60*
{code}
Following test cases were also failed but not captured in test run summary
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound Cou...
[ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
initialize ...
{noformat}
was:
{noformat}
*no* further _formatting_ is done here
{noformat}
{code:java}
[ERROR] Failures:
[ERROR] WidgetResourceProviderTest.testCreateResources:260
expected:<[[{"name":"value","name2":"value2"}]]> but was:<[[
{
"name": "value",
"name2": "value2"
}
]]>
[ERROR] WidgetResourceProviderTest.testUpdateResources:353
expected:<[[{"name":"new_value","new_name":"new_value2"}]]> but was:<[[
{
"name": "new_value",
"new_name": "new_value2"
}
]]>
[ERROR] Errors:
[ERROR] AmbariManagementControllerTest.testCreateActionsFailures:4332 ?
Ambari Action ...
[ERROR]
RootServiceComponentConfigurationResourceProviderTest.shouldUpdatePasswordInCredentialStoreIfSecurityPasswordEncryptionIsEnabled:534
? ConstructorNotFound
[ERROR] DDLTests.testCompareMySQL:134->compareAgainstPostgres:150 ?
UncheckedExecution
[ERROR] DDLTests.testVerifyMySQL:60->verifyDDL:89 ? UncheckedExecution
java.lang.Illeg...
[ERROR]
PasswordUtilsTest.shouldReadPasswordFromCredentialStoreOfAnAlias:67->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[ERROR]
PasswordUtilsTest.shouldResolveEncryptedPaswordIfWeStoreTheAliasInPasswordFile:103->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[INFO]
[ERROR] *Tests run: 5230, Failures: 2, Errors: 6, Skipped: 60*
{code}
Following test cases were also failed but not captured in test run summary
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound
[jira] [Assigned] (AMBARI-26037) ambari-server java test failures
[
https://issues.apache.org/jira/browse/AMBARI-26037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-26037:
Assignee: (was: Mohammad Arshad)
> ambari-server java test failures
>
>
> Key: AMBARI-26037
> URL: https://issues.apache.org/jira/browse/AMBARI-26037
> Project: Ambari
> Issue Type: Bug
>Reporter: Mohammad Arshad
>Priority: Major
>
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
> {code:java}
> [ERROR] Failures:
> [ERROR] WidgetResourceProviderTest.testCreateResources:260
> expected:<[[{"name":"value","name2":"value2"}]]> but was:<[[
> {
> "name": "value",
> "name2": "value2"
> }
> ]]>
> [ERROR] WidgetResourceProviderTest.testUpdateResources:353
> expected:<[[{"name":"new_value","new_name":"new_value2"}]]> but was:<[[
> {
> "name": "new_value",
> "new_name": "new_value2"
> }
> ]]>
> [ERROR] Errors:
> [ERROR] AmbariManagementControllerTest.testCreateActionsFailures:4332 ?
> Ambari Action ...
> [ERROR]
> RootServiceComponentConfigurationResourceProviderTest.shouldUpdatePasswordInCredentialStoreIfSecurityPasswordEncryptionIsEnabled:534
> ? ConstructorNotFound
> [ERROR] DDLTests.testCompareMySQL:134->compareAgainstPostgres:150 ?
> UncheckedExecution
> [ERROR] DDLTests.testVerifyMySQL:60->verifyDDL:89 ? UncheckedExecution
> java.lang.Illeg...
> [ERROR]
> PasswordUtilsTest.shouldReadPasswordFromCredentialStoreOfAnAlias:67->setupBasicCredentialProviderExpectations:127
> ? ConstructorNotFound
> [ERROR]
> PasswordUtilsTest.shouldResolveEncryptedPaswordIfWeStoreTheAliasInPasswordFile:103->setupBasicCredentialProviderExpectations:127
> ? ConstructorNotFound
> [INFO]
> [ERROR] *Tests run: 5230, Failures: 2, Errors: 6, Skipped: 60*
> {code}
> Following test cases were also failed but not captured in test run summary
> {noformat}
> [ERROR]
> AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
> ? AbstractMethod
> [ERROR]
> AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
> NoClassDefFound
> [ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
> javax.xml.parsers...
> [ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
> NoClassDefFound Could ...
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
> NoClassDefFound
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
> NoClassDefFound
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
> NoClassDefFound
> [ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
> NoClassDefFound Cou...
> [ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
> initialize ...
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26037) ambari-server java test failures
[
https://issues.apache.org/jira/browse/AMBARI-26037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-26037:
-
Description:
{noformat}
*no* further _formatting_ is done here
{noformat}
{code:java}
[ERROR] Failures:
[ERROR] WidgetResourceProviderTest.testCreateResources:260
expected:<[[{"name":"value","name2":"value2"}]]> but was:<[[
{
"name": "value",
"name2": "value2"
}
]]>
[ERROR] WidgetResourceProviderTest.testUpdateResources:353
expected:<[[{"name":"new_value","new_name":"new_value2"}]]> but was:<[[
{
"name": "new_value",
"new_name": "new_value2"
}
]]>
[ERROR] Errors:
[ERROR] AmbariManagementControllerTest.testCreateActionsFailures:4332 ?
Ambari Action ...
[ERROR]
RootServiceComponentConfigurationResourceProviderTest.shouldUpdatePasswordInCredentialStoreIfSecurityPasswordEncryptionIsEnabled:534
? ConstructorNotFound
[ERROR] DDLTests.testCompareMySQL:134->compareAgainstPostgres:150 ?
UncheckedExecution
[ERROR] DDLTests.testVerifyMySQL:60->verifyDDL:89 ? UncheckedExecution
java.lang.Illeg...
[ERROR]
PasswordUtilsTest.shouldReadPasswordFromCredentialStoreOfAnAlias:67->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[ERROR]
PasswordUtilsTest.shouldResolveEncryptedPaswordIfWeStoreTheAliasInPasswordFile:103->setupBasicCredentialProviderExpectations:127
? ConstructorNotFound
[INFO]
[ERROR] *Tests run: 5230, Failures: 2, Errors: 6, Skipped: 60*
{code}
Following test cases were also failed but not captured in test run summary
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound Cou...
[ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
initialize ...
{noformat}
was:
Following test cases in AmbariSwaggerReaderTest are failing consistently
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound Cou...
[ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
initialize ...
{noformat}
*Detailss*
{code:java}
[ERROR] Tests run: 8, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.08 s
<<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
[ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.034 s <<< ERROR!
java.lang.AbstractMethodError:
javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:70)
[ERROR] testJoinPaths(org.apache.ambari.swagger.AmbariSwaggerReaderTest) Time
elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.testJoinPaths(AmbariSwaggerReaderTest.java:60)
[ERROR]
swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:83)
[ERROR]
swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
[jira] [Updated] (AMBARI-26037) ambari-server java test failures
[
https://issues.apache.org/jira/browse/AMBARI-26037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-26037:
-
Summary: ambari-server java test failures (was: Correct
AmbariSwaggerReaderTest failures)
> ambari-server java test failures
>
>
> Key: AMBARI-26037
> URL: https://issues.apache.org/jira/browse/AMBARI-26037
> Project: Ambari
> Issue Type: Bug
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Following test cases in AmbariSwaggerReaderTest are failing consistently
> {noformat}
> [ERROR]
> AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
> ? AbstractMethod
> [ERROR]
> AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
> NoClassDefFound
> [ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
> javax.xml.parsers...
> [ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
> NoClassDefFound Could ...
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
> NoClassDefFound
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
> NoClassDefFound
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
> NoClassDefFound
> [ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
> NoClassDefFound Cou...
> [ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
> initialize ...
> {noformat}
> *Detailss*
> {code:java}
> [ERROR] Tests run: 8, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.08
> s <<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
> [ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.034 s <<< ERROR!
> java.lang.AbstractMethodError:
> javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:70)
> [ERROR] testJoinPaths(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.testJoinPaths(AmbariSwaggerReaderTest.java:60)
> [ERROR]
> swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:83)
> [ERROR]
> swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent(AmbariSwaggerReaderTest.java:100)
> [ERROR]
> swaggerConflictingNestedApisWithSamePreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent(AmbariSwaggerReaderTest.java:118)
> [ERROR]
> swaggerConflictingNestedApisWithBadPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent(AmbariSwaggerReaderTest.java:137)
> [ERROR]
> swaggerNestedApisWithOverwrite(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
> org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite(AmbariSwaggerReaderTest.java:154)
> [ERROR]
> swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ambari.swagger.AmbariSwaggerReader
> at
>
[jira] [Assigned] (AMBARI-26036) ambari-server python test failures
[
https://issues.apache.org/jira/browse/AMBARI-26036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-26036:
Assignee: (was: Mohammad Arshad)
> ambari-server python test failures
> --
>
> Key: AMBARI-26036
> URL: https://issues.apache.org/jira/browse/AMBARI-26036
> Project: Ambari
> Issue Type: Bug
>Reporter: Mohammad Arshad
>Priority: Major
>
> Following two test cases are failing in ambari branch-2.7
> test_start_secured (test_zeppelin_070.TestZeppelin070)
> testDBConnectionCheck (TestCheckHost.TestCheckHost)
> *Details*
> {code:java}
> FAIL: test_start_secured (test_zeppelin_070.TestZeppelin070)
> --
> Traceback (most recent call last):
> File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line
> 1199, in patched
> return func(*args, **keywargs)
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
> line 241, in test_start_secured
> dfs_type='',
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 345, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
> '/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled':
> False, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]..
> {code}
> {code:java}
> FAIL: testDBConnectionCheck (TestCheckHost.TestCheckHost)
> --
> Traceback (most recent call last):
> File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line
> 1199, in patched
> return func(*args, **keywargs)
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/custom_actions/TestCheckHost.py",
> line 163, in testDBConnectionCheck
> 'exit_code': 1}})
> AssertionError: {'db_connection_check': {'message': "'tuple' object has no
> attribute 'read'", 'e [truncated]... != {'db_connection_check': {'message':
> 'test message', 'exit_code': 1}}
> + {'db_connection_check': {'exit_code': 1, 'message': 'test message'}}
> - {'db_connection_check': {'exit_code': 1,
> - 'message': "'tuple' object has no attribute
> 'read'"}}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26034) Remove ambari-logsearch and ambari-infra from default build profiles
[
https://issues.apache.org/jira/browse/AMBARI-26034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805982#comment-17805982
]
Mohammad Arshad commented on AMBARI-26034:
--
# When tried to build ambari-logsearch, it failed with following error
{code:java}
mvn -B clean install rpm:rpm -DskipTests -Dpython.ver="python >= 2.6" -rf
:ambari-logsearch
{code}
{code:java}
package:
[INFO]
[INFO] Reactor Summary for ambari-logsearch 2.7.8.0.0:
[INFO]
[INFO] ambari-logsearch ... SUCCESS [ 0.805 s]
[INFO] Ambari Logsearch Appender .. FAILURE [ 1.029 s]
[INFO] Ambari Logsearch Config Api SKIPPED
[INFO] Ambari Logsearch Config JSON ... SKIPPED
[INFO] Ambari Logsearch Config Solr ... SKIPPED
[INFO] Ambari Logsearch Config Zookeeper .. SKIPPED
[INFO] Ambari Logsearch Config Local .. SKIPPED
[INFO] Ambari Logsearch Log Feeder Plugin Api . SKIPPED
[INFO] Ambari Logsearch Log Feeder Container Registry . SKIPPED
[INFO] Ambari Logsearch Log Feeder SKIPPED
[INFO] Ambari Logsearch Web ... SKIPPED
[INFO] Ambari Logsearch Server SKIPPED
[INFO] Ambari Logsearch Assembly .. SKIPPED
[INFO] Ambari Logsearch Integration Test .. SKIPPED
[INFO] ambari-infra ... SKIPPED
[INFO] Ambari Infra Solr Client ... SKIPPED
[INFO] Ambari Infra Solr Plugin ... SKIPPED
[INFO] Ambari Infra Manager ... SKIPPED
[INFO] Ambari Infra Assembly .. SKIPPED
[INFO] Ambari Infra Manager Integration Tests . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.231 s
[INFO] Finished at: 2024-01-12T09:56:53Z
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
ambari-logsearch-appender: An Ant BuildException has occured: The following
error occurred while executing this line:
[ERROR] /ws/ambari-2.7/ambari-logsearch/ambari-logsearch-appender/build.xml:35:
/ws/ambari-2.7/ambari-logsearch/ambari-logsearch-appender/target/package does
not exist.
[ERROR] around Ant part .. @ 4:28 in
/ws/ambari-2.7/ambari-logsearch/ambari-logsearch-appender/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :ambari-logsearch-appender
[user@id ambari-2.7]#
{code}
# When I tried to build ambari-infra, it failed with following error
{noformat}
mvn -B clean install rpm:rpm -DskipTests -Dpython.ver="python >= 2.6" -rf
:ambari-infra
{noformat}
{code:java}
[INFO] ambari-infra ... SUCCESS [ 0.751 s]
[INFO] Ambari Infra Solr Client ... SUCCESS [ 5.505 s]
[INFO] Ambari Infra Solr Plugin ... FAILURE [ 1.064 s]
[INFO] Ambari Infra Manager ... SKIPPED
[INFO] Ambari Infra Assembly .. SKIPPED
[INFO] Ambari Infra Manager Integration Tests . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.810 s
[INFO] Finished at: 2024-01-12T09:58:15Z
[INFO]
[ERROR] Failed to execute goal on project ambari-infra-solr-plugin: Could not
resolve dependencies for project
org.apache.ambari:ambari-infra-solr-plugin:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
[jira] [Updated] (AMBARI-26037) Correct AmbariSwaggerReaderTest failures
[
https://issues.apache.org/jira/browse/AMBARI-26037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-26037:
-
Description:
Following test cases in AmbariSwaggerReaderTest are failing consistently
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound Cou...
[ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
initialize ...
{noformat}
*Detailss*
{code:java}
[ERROR] Tests run: 8, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.08 s
<<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
[ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.034 s <<< ERROR!
java.lang.AbstractMethodError:
javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:70)
[ERROR] testJoinPaths(org.apache.ambari.swagger.AmbariSwaggerReaderTest) Time
elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.testJoinPaths(AmbariSwaggerReaderTest.java:60)
[ERROR]
swaggerConflictingNestedApis(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApis(AmbariSwaggerReaderTest.java:83)
[ERROR]
swaggerConflictingNestedApisWithPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent(AmbariSwaggerReaderTest.java:100)
[ERROR]
swaggerConflictingNestedApisWithSamePreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent(AmbariSwaggerReaderTest.java:118)
[ERROR]
swaggerConflictingNestedApisWithBadPreferredParent(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent(AmbariSwaggerReaderTest.java:137)
[ERROR]
swaggerNestedApisWithOverwrite(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite(AmbariSwaggerReaderTest.java:154)
[ERROR]
swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel(org.apache.ambari.swagger.AmbariSwaggerReaderTest)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ambari.swagger.AmbariSwaggerReader
at
org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel(AmbariSwaggerReaderTest.java:170)
{code}
was:
Following test cases in AmbariSwaggerReaderTest are failing consistently
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
[jira] [Created] (AMBARI-26037) Correct AmbariSwaggerReaderTest failures
Mohammad Arshad created AMBARI-26037:
Summary: Correct AmbariSwaggerReaderTest failures
Key: AMBARI-26037
URL: https://issues.apache.org/jira/browse/AMBARI-26037
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Following test cases in AmbariSwaggerReaderTest are failing consistently
{noformat}
[ERROR]
AvoidTransactionalOnPrivateMethodsCheckTest.transactionalOnPrivateMethod:46->BaseCheckTestSupport.verify:121->BaseCheckTestSupport.createChecker:60
? AbstractMethod
[ERROR]
AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:170
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:70 ? AbstractMethod
javax.xml.parsers...
[ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:83
NoClassDefFound Could ...
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:137
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:100
NoClassDefFound
[ERROR]
AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:118
NoClassDefFound
[ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:154
NoClassDefFound Cou...
[ERROR] AmbariSwaggerReaderTest.testJoinPaths:60 NoClassDefFound Could not
initialize ...
{noformat}
*Detailss*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26036) ambari-server python test failures
[
https://issues.apache.org/jira/browse/AMBARI-26036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805905#comment-17805905
]
Mohammad Arshad commented on AMBARI-26036:
--
test_start_secured (test_zeppelin_070.TestZeppelin070) is even failing in
release 2.7.7
{code:java}
FAIL: test_start_secured (test_zeppelin_070.TestZeppelin070)
--
Traceback (most recent call last):
File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line 1199,
in patched
return func(*args, **keywargs)
File
"/ws/ambari-2.7/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
line 241, in test_start_secured
dfs_type='',
File
"/ws/ambari-2.7/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 345, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
'/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled': False,
'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]...
{'action': ['create_on_execute'],
'default_fs': u'hdfs://c6401.ambari.apache.org:8020',
'dfs_type': '',
- 'hadoop_bin_dir': '/usr/hdp/2.5.0.0-1235/hadoop/bin',
{code}
> ambari-server python test failures
> --
>
> Key: AMBARI-26036
> URL: https://issues.apache.org/jira/browse/AMBARI-26036
> Project: Ambari
> Issue Type: Bug
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Following two test cases are failing in ambari branch-2.7
> test_start_secured (test_zeppelin_070.TestZeppelin070)
> testDBConnectionCheck (TestCheckHost.TestCheckHost)
> *Details*
> {code:java}
> FAIL: test_start_secured (test_zeppelin_070.TestZeppelin070)
> --
> Traceback (most recent call last):
> File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line
> 1199, in patched
> return func(*args, **keywargs)
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
> line 241, in test_start_secured
> dfs_type='',
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 345, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
> '/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled':
> False, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]..
> {code}
> {code:java}
> FAIL: testDBConnectionCheck (TestCheckHost.TestCheckHost)
> --
> Traceback (most recent call last):
> File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line
> 1199, in patched
> return func(*args, **keywargs)
> File
> "/ws/ambari-2.7/ambari-server/src/test/python/custom_actions/TestCheckHost.py",
> line 163, in testDBConnectionCheck
> 'exit_code': 1}})
> AssertionError: {'db_connection_check': {'message': "'tuple' object has no
> attribute 'read'", 'e [truncated]... != {'db_connection_check': {'message':
> 'test message', 'exit_code': 1}}
> + {'db_connection_check': {'exit_code': 1, 'message': 'test message'}}
> - {'db_connection_check': {'exit_code': 1,
> - 'message': "'tuple' object has no attribute
> 'read'"}}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26036) ambari-server python test failures
Mohammad Arshad created AMBARI-26036:
Summary: ambari-server python test failures
Key: AMBARI-26036
URL: https://issues.apache.org/jira/browse/AMBARI-26036
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Following two test cases are failing in ambari branch-2.7
test_start_secured (test_zeppelin_070.TestZeppelin070)
testDBConnectionCheck (TestCheckHost.TestCheckHost)
*Details*
{code:java}
FAIL: test_start_secured (test_zeppelin_070.TestZeppelin070)
--
Traceback (most recent call last):
File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line 1199,
in patched
return func(*args, **keywargs)
File
"/ws/ambari-2.7/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
line 241, in test_start_secured
dfs_type='',
File
"/ws/ambari-2.7/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 345, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
'/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled': False,
'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]..
{code}
{code:java}
FAIL: testDBConnectionCheck (TestCheckHost.TestCheckHost)
--
Traceback (most recent call last):
File "/ws/ambari-2.7/ambari-common/src/test/python/mock/mock.py", line 1199,
in patched
return func(*args, **keywargs)
File
"/ws/ambari-2.7/ambari-server/src/test/python/custom_actions/TestCheckHost.py",
line 163, in testDBConnectionCheck
'exit_code': 1}})
AssertionError: {'db_connection_check': {'message': "'tuple' object has no
attribute 'read'", 'e [truncated]... != {'db_connection_check': {'message':
'test message', 'exit_code': 1}}
+ {'db_connection_check': {'exit_code': 1, 'message': 'test message'}}
- {'db_connection_check': {'exit_code': 1,
- 'message': "'tuple' object has no attribute 'read'"}}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26035) Ambari PR CI is failing
Mohammad Arshad created AMBARI-26035:
Summary: Ambari PR CI is failing
Key: AMBARI-26035
URL: https://issues.apache.org/jira/browse/AMBARI-26035
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Ambari PR CI is failing with following errors
{code:java}
INFO] Storing buildScmBranch: UNKNOWN
[INFO]
[INFO] --- exec:1.2.1:exec (azuredb-gen) @ ambari-server ---
/usr/bin/env: ‘python’: No such file or directory
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main 2.7.8.0.0 .. SUCCESS [ 0.592 s]
[INFO] Apache Ambari Project POM 2.7.8.0.0 SUCCESS [ 0.004 s]
[INFO] Ambari Views 2.7.8.0.0 . SUCCESS [ 1.884 s]
[INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 1.920 s]
[INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.144 s]
[INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 0.221 s]
[INFO] Ambari Service Advisor 1.0.0.0-SNAPSHOT SUCCESS [ 0.263 s]
[INFO] Ambari Server 2.7.8.0.0 FAILURE [ 1.451 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6.959 s
[INFO] Finished at: 2024-01-11T09:37:26Z
[INFO]
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
(azuredb-gen) on project ambari-server: Command execution failed.: Process
exited with an error: 127 (Exit value: 127) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26034) Remove ambari-logsearch and ambari-infra from default build profiles
[ https://issues.apache.org/jira/browse/AMBARI-26034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26034: - Summary: Remove ambari-logsearch and ambari-infra from default build profiles (was: Remove ambari-logsearch and ambari-infra from default default build profiles) > Remove ambari-logsearch and ambari-infra from default build profiles > > > Key: AMBARI-26034 > URL: https://issues.apache.org/jira/browse/AMBARI-26034 > Project: Ambari > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > > ambari-logsearch and ambari-infra are not maintained from long time. > Also these projects are moved to following sub projects and have separate git > repository. > https://github.com/apache/ambari-logsearch > https://github.com/apache/ambari-infra > Can not remove these codes from branch-2.7 at this point in time and I think > it is ok to not build these projects by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26034) Remove ambari-logsearch and ambari-infra from default default build profiles
Mohammad Arshad created AMBARI-26034: Summary: Remove ambari-logsearch and ambari-infra from default default build profiles Key: AMBARI-26034 URL: https://issues.apache.org/jira/browse/AMBARI-26034 Project: Ambari Issue Type: Bug Reporter: Mohammad Arshad Assignee: Mohammad Arshad ambari-logsearch and ambari-infra are not maintained from long time. Also these projects are moved to following sub projects and have separate git repository. https://github.com/apache/ambari-logsearch https://github.com/apache/ambari-infra Can not remove these codes from branch-2.7 at this point in time and I think it is ok to not build these projects by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26033) Release Ambari 2.7.8
Mohammad Arshad created AMBARI-26033: Summary: Release Ambari 2.7.8 Key: AMBARI-26033 URL: https://issues.apache.org/jira/browse/AMBARI-26033 Project: Ambari Issue Type: Task Reporter: Mohammad Arshad Assignee: Mohammad Arshad -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26032) WidgetResourceProvider wrong import order causing compilation failure
Mohammad Arshad created AMBARI-26032:
Summary: WidgetResourceProvider wrong import order causing
compilation failure
Key: AMBARI-26032
URL: https://issues.apache.org/jira/browse/AMBARI-26032
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
WidgetResourceProvider wrong import order causing compilation failure
{noformat}
[ERROR]
/ws/ambari-2.7/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/WidgetResourceProvider.java:58:
Wrong order for 'com.google.gson.JsonElement' import. [ImportOrder]
[ERROR]
/ws/ambari-2.7/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/WidgetResourceProvider.java:60:
Wrong order for 'com.google.gson.JsonPrimitive' import. [ImportOrder]
Audit done.
[INFO]
[INFO] Reactor Summary for Ambari Server 2.7.8.0.0:
[INFO]
[INFO] Ambari Server .. FAILURE [ 30.156 s]
[INFO] Ambari Functional Tests SKIPPED
[INFO] Ambari Agent ... SKIPPED
[INFO] ambari-logsearch ... SKIPPED
[INFO] Ambari Logsearch Appender .. SKIPPED
[INFO] Ambari Logsearch Config Api SKIPPED
[INFO] Ambari Logsearch Config JSON ... SKIPPED
[INFO] Ambari Logsearch Config Solr ... SKIPPED
[INFO] Ambari Logsearch Config Zookeeper .. SKIPPED
[INFO] Ambari Logsearch Config Local .. SKIPPED
[INFO] Ambari Logsearch Log Feeder Plugin Api . SKIPPED
[INFO] Ambari Logsearch Log Feeder Container Registry . SKIPPED
[INFO] Ambari Logsearch Log Feeder SKIPPED
[INFO] Ambari Logsearch Web ... SKIPPED
[INFO] Ambari Logsearch Server SKIPPED
[INFO] Ambari Logsearch Assembly .. SKIPPED
[INFO] Ambari Logsearch Integration Test .. SKIPPED
[INFO] ambari-infra ... SKIPPED
[INFO] Ambari Infra Solr Client ... SKIPPED
[INFO] Ambari Infra Solr Plugin ... SKIPPED
[INFO] Ambari Infra Manager ... SKIPPED
[INFO] Ambari Infra Assembly .. SKIPPED
[INFO] Ambari Infra Manager Integration Tests . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 30.594 s
[INFO] Finished at: 2024-01-10T16:16:51Z
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
project ambari-server: Failed during checkstyle execution: There are 2 errors
reported by Checkstyle 6.19 with /ws/ambari-2.7/ambari-server/checkstyle.xml
ruleset. -> [Help 1]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25985) Remove PhantomJs as a headless web browser
[ https://issues.apache.org/jira/browse/AMBARI-25985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-25985. -- Fix Version/s: 3.0.0 Resolution: Fixed > Remove PhantomJs as a headless web browser > -- > > Key: AMBARI-25985 > URL: https://issues.apache.org/jira/browse/AMBARI-25985 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: vanshuhassija >Priority: Minor > Fix For: 3.0.0 > > Original Estimate: 48h > Time Spent: 1.5h > Remaining Estimate: 46.5h > > PhantomJS is a headless web browser scriptable with JavaScript. The package > is no longer maintained and does not even support ES6 features of Javascript. > Chrome launched ChromeHeadless which works very similar to PhantomJs. The fix > will require Karma to use ChromeHeadless as the web browser instead of > PhantomJs -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25985) Remove PhantomJs as a headless web browser
[ https://issues.apache.org/jira/browse/AMBARI-25985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787866#comment-17787866 ] Mohammad Arshad commented on AMBARI-25985: -- Merged to trunk. Thanks [~vanshuhassija] for your contribution. > Remove PhantomJs as a headless web browser > -- > > Key: AMBARI-25985 > URL: https://issues.apache.org/jira/browse/AMBARI-25985 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: vanshuhassija >Priority: Minor > Fix For: 3.0.0 > > Original Estimate: 48h > Time Spent: 1.5h > Remaining Estimate: 46.5h > > PhantomJS is a headless web browser scriptable with JavaScript. The package > is no longer maintained and does not even support ES6 features of Javascript. > Chrome launched ChromeHeadless which works very similar to PhantomJs. The fix > will require Karma to use ChromeHeadless as the web browser instead of > PhantomJs -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26019) Ambari-server log is filled with ClusterNotFoundException when no cluster is installed
Mohammad Arshad created AMBARI-26019:
Summary: Ambari-server log is filled with ClusterNotFoundException
when no cluster is installed
Key: AMBARI-26019
URL: https://issues.apache.org/jira/browse/AMBARI-26019
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Ambari-server log is filled with ClusterNotFoundException when no cluster is
installed
{code:java}
2023-10-27 18:44:43,135 ERROR [agent-command-publisher-3]
AgentCommandsPublisher:116 - Exception on sendAgentCommand
org.apache.ambari.server.ClusterNotFoundException: Cluster not found,
clusterId=-1
at
org.apache.ambari.server.state.cluster.ClustersImpl.getCluster(ClustersImpl.java:417)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:113)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
at
com.google.common.collect.CollectSpliterators$1.forEachRemaining(CollectSpliterators.java:116)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.lambda$forEachRemaining$1(CollectSpliterators.java:247)
at
java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1723)
at
com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.forEachRemaining(CollectSpliterators.java:247)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
at
java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
at
org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$sendAgentCommand$1(AgentCommandsPublisher.java:104)
at
java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at
java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at
java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26014) Ambari Functional Test execution is failing
[ https://issues.apache.org/jira/browse/AMBARI-26014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1870#comment-1870 ] Mohammad Arshad commented on AMBARI-26014: -- After fix GetStacksTest and RoleBasedAccessControlBasicTest running successfully. Created another bug for DeleteServiceTest test case correction. !screenshot-1.png! > Ambari Functional Test execution is failing > --- > > Key: AMBARI-26014 > URL: https://issues.apache.org/jira/browse/AMBARI-26014 > Project: Ambari > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > > # ambari-funtest module contains few functional test cases. These test cases > verify functionality on real(without using mock) ambari server. These test > cases are really useful in verifying new functionality quickly. But these > test cases have very basic issues and failing consistently. These test cases > need to be fixed. > # These functional test cases are disabled and skip=true is hard coded, i > think it is better to make the skip configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26014) Ambari Functional Test execution is failing
[ https://issues.apache.org/jira/browse/AMBARI-26014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26014: - Attachment: screenshot-1.png > Ambari Functional Test execution is failing > --- > > Key: AMBARI-26014 > URL: https://issues.apache.org/jira/browse/AMBARI-26014 > Project: Ambari > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > > # ambari-funtest module contains few functional test cases. These test cases > verify functionality on real(without using mock) ambari server. These test > cases are really useful in verifying new functionality quickly. But these > test cases have very basic issues and failing consistently. These test cases > need to be fixed. > # These functional test cases are disabled and skip=true is hard coded, i > think it is better to make the skip configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26015) Fix DeleteServiceTest functional test case
Mohammad Arshad created AMBARI-26015:
Summary: Fix DeleteServiceTest functional test case
Key: AMBARI-26015
URL: https://issues.apache.org/jira/browse/AMBARI-26015
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
org.apache.ambari.funtest.server.tests.DeleteServiceTest#testDeleteService
failing with following error.
{code:java}
2023-10-20 22:09:04,209 ERROR [pool-4-thread-1] EventBus.ambari-event-bus
(EventBus.java:handleException(232)) - Exception thrown by subscriber method
onHostStateUpdate(org.apache.ambari.server.events.HostStateUpdateEvent) on
subscriber
org.apache.ambari.server.events.listeners.hosts.HostUpdateListener@2bcec6a6
when dispatching event: HostStateUpdateEvent{eventType=HOST_STATE_CHANGE}
org.apache.ambari.server.HostNotFoundException: Host not found, hostname=host1
at
org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:457)
at
org.apache.ambari.server.events.listeners.hosts.HostUpdateListener.onHostStateUpdate(HostUpdateListener.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:87)
at
com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:144)
at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:72)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
{code:java}
023-10-20 22:09:04,734 ERROR [stomp-agent-bus-0] EventBus.agent-update-bus
(EventBus.java:handleException(232)) - Exception thrown by subscriber method
onUpdateEvent(org.apache.ambari.server.events.STOMPEvent) on subscriber
org.apache.ambari.server.events.listeners.requests.STOMPUpdateListener@3d83bfb9
when dispatching event:
org.apache.ambari.server.events.AgentConfigsUpdateEvent@4bc6f34
org.apache.ambari.server.HostNotRegisteredException: Host with hostId '1' not
registered
at
org.apache.ambari.server.HostNotRegisteredException.forHostId(HostNotRegisteredException.java:31)
at
org.apache.ambari.server.agent.AgentSessionManager.getSessionId(AgentSessionManager.java:70)
at
org.apache.ambari.server.events.MessageEmitter.emitMessageToHost(MessageEmitter.java:170)
at
org.apache.ambari.server.events.DefaultMessageEmitter.emitMessage(DefaultMessageEmitter.java:99)
at
org.apache.ambari.server.events.listeners.requests.STOMPUpdateListener.onUpdateEvent(STOMPUpdateListener.java:53)
at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:87)
{code}
{code:java}
2023-10-20 22:09:04,751 ERROR [ambari-client-thread-31] handlers.CreateHandler
(CreateHandler.java:persist(80)) - Bad request received: No repositories were
found for service installation
java.lang.IllegalArgumentException: No repositories were found for service
installation
at
org.apache.ambari.server.controller.internal.ServiceResourceProvider.validateCreateRequests(ServiceResourceProvider.java:1178)
at
org.apache.ambari.server.controller.internal.ServiceResourceProvider.createServices(ServiceResourceProvider.java:508)
at
org.apache.ambari.server.controller.internal.ServiceResourceProvider$1.invoke(ServiceResourceProvider.java:278)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26014) Ambari Functional Test execution is failing
Mohammad Arshad created AMBARI-26014: Summary: Ambari Functional Test execution is failing Key: AMBARI-26014 URL: https://issues.apache.org/jira/browse/AMBARI-26014 Project: Ambari Issue Type: Bug Reporter: Mohammad Arshad Assignee: Mohammad Arshad # ambari-funtest module contains few functional test cases. These test cases verify functionality on real(without using mock) ambari server. These test cases are really useful in verifying new functionality quickly. But these test cases have very basic issues and failing consistently. These test cases need to be fixed. # These functional test cases are disabled and skip=true is hard coded, i think it is better to make the skip configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-26004) Support Ambari agent test case execution on Python3 environment
[ https://issues.apache.org/jira/browse/AMBARI-26004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-26004. -- Resolution: Done > Support Ambari agent test case execution on Python3 environment > --- > > Key: AMBARI-26004 > URL: https://issues.apache.org/jira/browse/AMBARI-26004 > Project: Ambari > Issue Type: Task > Components: build >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-26004) Support Ambari agent test case execution on Python3 environment
[
https://issues.apache.org/jira/browse/AMBARI-26004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767931#comment-17767931
]
Mohammad Arshad commented on AMBARI-26004:
--
Changed Ambari-PreCommit-GitHub-PR CI script to install distro package before
executing ambari agent test cases
{noformat}
stage('Ambari Agent Tests') {
steps {
sh 'pip3 install distro'
sh 'mvn -Dmaven.test.failure.ignore=true -am test -pl ambari-agent
-Dmaven.artifact.threads=10 -Drat.skip'
}
}
{noformat}
Builds are passing now
https://ci-hadoop.apache.org/blue/organizations/jenkins/Ambari%2FAmbari-PreCommit-GitHub-PR/detail/PR-3754/2/pipeline/
!screenshot-1.png!
> Support Ambari agent test case execution on Python3 environment
> ---
>
> Key: AMBARI-26004
> URL: https://issues.apache.org/jira/browse/AMBARI-26004
> Project: Ambari
> Issue Type: Task
> Components: build
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26004) Support Ambari agent test case execution on Python3 environment
[ https://issues.apache.org/jira/browse/AMBARI-26004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-26004: - Attachment: screenshot-1.png > Support Ambari agent test case execution on Python3 environment > --- > > Key: AMBARI-26004 > URL: https://issues.apache.org/jira/browse/AMBARI-26004 > Project: Ambari > Issue Type: Task > Components: build >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-26004) Support Ambari agent test case execution on Python3 environment
Mohammad Arshad created AMBARI-26004: Summary: Support Ambari agent test case execution on Python3 environment Key: AMBARI-26004 URL: https://issues.apache.org/jira/browse/AMBARI-26004 Project: Ambari Issue Type: Task Components: build Reporter: Mohammad Arshad Assignee: Mohammad Arshad -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25995) Resolve mutate related graphs for hbase & ams-hbase
[ https://issues.apache.org/jira/browse/AMBARI-25995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762964#comment-17762964 ] Mohammad Arshad commented on AMBARI-25995: -- Thanks [~skumar34] for your contribution. Merged to ambari trunk and metrics master branch. [https://github.com/apache/ambari/commit/d439b213348e44fc2d6892437c725d61d731ac7c] [https://github.com/apache/ambari-metrics/commit/a565e2a79256a39788c012df3f0d89798156bc89] > Resolve mutate related graphs for hbase & ams-hbase > --- > > Key: AMBARI-25995 > URL: https://issues.apache.org/jira/browse/AMBARI-25995 > Project: Ambari > Issue Type: Story >Reporter: Sandeep Kumar >Assignee: Sandeep Kumar >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0, metrics-3.1.0 > > Attachments: HbaseHomePutLatencies.png, > HbaseRegionServersNumRequestsPut.png, > HbaseRegionserverOperationLatenciesPut.png, > amsHbaseHomeOperationLatenciesPut.png, amsHbaseNumPutRequests.png, > amsHbaseOperationLatenciesPut.png, image-2023-08-22-00-51-53-101.png, > image-2023-08-22-00-55-55-893.png, image-2023-08-22-00-56-40-536.png, > image-2023-08-22-00-58-18-615.png, image-2023-08-22-00-58-26-998.png, > image-2023-08-22-00-59-35-889.png, image-2023-08-22-01-00-22-674.png > > Time Spent: 20m > Remaining Estimate: 0h > > These graphs are showing no data > AMS-hbase home: > !image-2023-08-22-00-51-53-101.png|width=451,height=148! > ams-hbase-regionserver: > !image-2023-08-22-00-55-55-893.png|width=444,height=162! > !image-2023-08-22-00-56-40-536.png|width=450,height=195! > HBase-home: > !image-2023-08-22-00-58-26-998.png|width=445,height=127! > Hbase-regionserver: > !image-2023-08-22-01-00-22-674.png|width=406,height=148! > !image-2023-08-22-00-59-35-889.png|width=408,height=177! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25995) Resolve mutate related graphs for hbase & ams-hbase
[ https://issues.apache.org/jira/browse/AMBARI-25995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad resolved AMBARI-25995. -- Fix Version/s: 2.8.0 metrics-3.1.0 Resolution: Fixed > Resolve mutate related graphs for hbase & ams-hbase > --- > > Key: AMBARI-25995 > URL: https://issues.apache.org/jira/browse/AMBARI-25995 > Project: Ambari > Issue Type: Story >Reporter: Sandeep Kumar >Assignee: Sandeep Kumar >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0, metrics-3.1.0 > > Attachments: HbaseHomePutLatencies.png, > HbaseRegionServersNumRequestsPut.png, > HbaseRegionserverOperationLatenciesPut.png, > amsHbaseHomeOperationLatenciesPut.png, amsHbaseNumPutRequests.png, > amsHbaseOperationLatenciesPut.png, image-2023-08-22-00-51-53-101.png, > image-2023-08-22-00-55-55-893.png, image-2023-08-22-00-56-40-536.png, > image-2023-08-22-00-58-18-615.png, image-2023-08-22-00-58-26-998.png, > image-2023-08-22-00-59-35-889.png, image-2023-08-22-01-00-22-674.png > > Time Spent: 20m > Remaining Estimate: 0h > > These graphs are showing no data > AMS-hbase home: > !image-2023-08-22-00-51-53-101.png|width=451,height=148! > ams-hbase-regionserver: > !image-2023-08-22-00-55-55-893.png|width=444,height=162! > !image-2023-08-22-00-56-40-536.png|width=450,height=195! > HBase-home: > !image-2023-08-22-00-58-26-998.png|width=445,height=127! > Hbase-regionserver: > !image-2023-08-22-01-00-22-674.png|width=406,height=148! > !image-2023-08-22-00-59-35-889.png|width=408,height=177! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25998) Host uuid is not getting synced to other collectors, causing NPE while accessing metric
Mohammad Arshad created AMBARI-25998:
Summary: Host uuid is not getting synced to other collectors,
causing NPE while accessing metric
Key: AMBARI-25998
URL: https://issues.apache.org/jira/browse/AMBARI-25998
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Host uuid is not getting synced with other collectors, causing NPE while
accessing metric
{code:java}
java.lang.NullPointerException
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457)
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150)
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966)
at
org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294)
at
org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267)
{code}
*Steps to reproduce the issue*
1. Push below metrics through collector-1
{noformat}
{
"metrics": [
{
"metricname": "cpu1",
"appid": "app1",
"hostname": "host1",
"starttime": 1693294119309,
"metrics": {
"1693294119309": 100,
"1693294129309": 200
}
}
]
}
{noformat}
After metadata sync interval elapsed, performed following operations
2. GET http://COLLECTOR-1-HOST:6188/ws/v1/timeline/metrics/hosts returned
{noformat}
{
"host1": [
"app1"
],
...
}
{noformat}
3. GET http://COLLECTOR-2-HOST:6188/ws/v1/timeline/metrics/hosts returned
{
"host1": [
"app1"
],
...
}
4. GET
http://COLLECTOR-1-HOST:6188/ws/v1/timeline/metrics?metricNames=cpu1=app1=host1
returned
{
"metrics": [
{
"metricname": "cpu1",
"appid": "app1",
"hostname": "host1",
"timestamp": 0,
"starttime": 1693294119309,
"metrics": {
"1693294129309": 200.0
},
"metadata": {}
}
]
}
5. GET
http://COLLECTOR-2-HOST:6188/ws/v1/timeline/metrics?metricNames=cpu1=app1=host1
returned
{noformat}
{
"exception": "NullPointerException",
"javaClassName": "java.lang.NullPointerException"
}
{noformat}
When host name is being synced, host id also should be synced to fix this issue.
Similar to this issue another issue
https://issues.apache.org/jira/browse/AMBARI-25963 was raised, but that NPE was
because metrics uuid was not synced, this issue is because of host uuid is not
synced.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
[
https://issues.apache.org/jira/browse/AMBARI-25977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754083#comment-17754083
]
Mohammad Arshad commented on AMBARI-25977:
--
Thanks [~brahmareddy] for reviewing and merging the PR.
> Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
> ---
>
> Key: AMBARI-25977
> URL: https://issues.apache.org/jira/browse/AMBARI-25977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.8.0, 2.7.8
>
> Attachments: screenshot-1.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number
> of records in a batch by default are set to 1, some times this value is
> not sufficient and collector fails, to store aggregated data, with following
> error
> {code:java}
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858209
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
> 1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
> 1690284122957=133.09041926456285}
> 2023-07-25 11:21:21,597 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858964
> 2023-07-25 11:21:21,598 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
> 1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
> 1690284122957=195.3577965382318}
> {code}
> lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
> more reasonable with batch size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[
https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753961#comment-17753961
]
Mohammad Arshad commented on AMBARI-25984:
--
Thanks [~vishalsuvagia] for the reviewing and merging the PR.
> Ambari metrics summary API missing daily aggregator info
>
>
> Key: AMBARI-25984
> URL: https://issues.apache.org/jira/browse/AMBARI-25984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0, metrics-3.1.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
> {noformat}
> {
> "timestamp": 1691405233095,
> "metadata": {
> "timeline_metric_store_watcher": "2",
> "datanode": "329",
> "HOST": "154",
> "jobhistoryserver": "67",
> "namenode": "457",
> "ambari_server": "79",
> "hiveserver2": "116",
> "amssmoketestfake": "2",
> "hivemetastore": "438",
> "resourcemanager": "257",
> "Number of Hosts": "7",
> "applicationhistoryserver": "108",
> "nodemanager": "366",
> "hbase": "1950",
> "ams-hbase": "5583"
> },
> "aggregation": {
> "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
> "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
> "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
> }
> }
> {noformat}
> In above aggregation information TimelineMetricHostAggregatorDaily and
> TimelineClusterAggregatorDaily are missing. Summary API should return these
> aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[
https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad resolved AMBARI-25984.
--
Fix Version/s: 2.8.0
metrics-3.1.0
Resolution: Fixed
> Ambari metrics summary API missing daily aggregator info
>
>
> Key: AMBARI-25984
> URL: https://issues.apache.org/jira/browse/AMBARI-25984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0, metrics-3.1.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
> {noformat}
> {
> "timestamp": 1691405233095,
> "metadata": {
> "timeline_metric_store_watcher": "2",
> "datanode": "329",
> "HOST": "154",
> "jobhistoryserver": "67",
> "namenode": "457",
> "ambari_server": "79",
> "hiveserver2": "116",
> "amssmoketestfake": "2",
> "hivemetastore": "438",
> "resourcemanager": "257",
> "Number of Hosts": "7",
> "applicationhistoryserver": "108",
> "nodemanager": "366",
> "hbase": "1950",
> "ams-hbase": "5583"
> },
> "aggregation": {
> "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
> "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
> "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
> }
> }
> {noformat}
> In above aggregation information TimelineMetricHostAggregatorDaily and
> TimelineClusterAggregatorDaily are missing. Summary API should return these
> aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25963) Metrics metadata sync problem, accessing metrics which got created though other collector throws NPE
[
https://issues.apache.org/jira/browse/AMBARI-25963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753960#comment-17753960
]
Mohammad Arshad commented on AMBARI-25963:
--
Thanks [~vjasani], [~brahmareddy] for review.
Thanks [~vishalsuvagia] for review and merge.
> Metrics metadata sync problem, accessing metrics which got created though
> other collector throws NPE
>
>
> Key: AMBARI-25963
> URL: https://issues.apache.org/jira/browse/AMBARI-25963
> Project: Ambari
> Issue Type: Bug
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0, metrics-3.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Metrics metadata sync problem, accessing metrics which got created though
> other collector throws NPE
> *Steps to reproduce the issue:*
> # Install ambari metrics with two collectors C1 and C2
> # Submit following metrics through collector C1
> {code:java}
> {
> "metrics": [
> {
> "metricname": "cpu",
> "appid": "skywalking",
> "hostname": "hostXYZ",
> "starttime": 1687944230477,
> "metrics": {
> "1687944230477": 100,
> "1687944430477": 200
> }
> }
> ]
> }
> {code}
> #
> http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics?metricNames=cpu=skywalking=hostXYZ
> API call returns
> {noformat}
> {
> "exception": "NullPointerException",
> "javaClassName": "java.lang.NullPointerException"
> }
> {noformat}
> In collector C2 log file following message is logged
> {code}
> 2023-06-28 09:40:24,592 ERROR
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> TimelineMetricMetadataKey is null for : [7, 73, 67, -94, 19, -102, 82, 114,
> 100, -66, -22, 79, -51, -107, -73, 64, -36, -72, -42, -103]
> 2023-06-28 09:40:24,594 WARN
> org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
> java.lang.NullPointerException
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457)
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150)
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966)
> at
> org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294)
> at
> org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267)
> {code}
> Same behaviour is there even after 5 minutes which is the default ambari
> metrics metadata sync interval.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25963) Metrics metadata sync problem, accessing metrics which got created though other collector throws NPE
[
https://issues.apache.org/jira/browse/AMBARI-25963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad resolved AMBARI-25963.
--
Fix Version/s: 2.8.0
metrics-3.1.0
Resolution: Fixed
> Metrics metadata sync problem, accessing metrics which got created though
> other collector throws NPE
>
>
> Key: AMBARI-25963
> URL: https://issues.apache.org/jira/browse/AMBARI-25963
> Project: Ambari
> Issue Type: Bug
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0, metrics-3.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Metrics metadata sync problem, accessing metrics which got created though
> other collector throws NPE
> *Steps to reproduce the issue:*
> # Install ambari metrics with two collectors C1 and C2
> # Submit following metrics through collector C1
> {code:java}
> {
> "metrics": [
> {
> "metricname": "cpu",
> "appid": "skywalking",
> "hostname": "hostXYZ",
> "starttime": 1687944230477,
> "metrics": {
> "1687944230477": 100,
> "1687944430477": 200
> }
> }
> ]
> }
> {code}
> #
> http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics?metricNames=cpu=skywalking=hostXYZ
> API call returns
> {noformat}
> {
> "exception": "NullPointerException",
> "javaClassName": "java.lang.NullPointerException"
> }
> {noformat}
> In collector C2 log file following message is logged
> {code}
> 2023-06-28 09:40:24,592 ERROR
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> TimelineMetricMetadataKey is null for : [7, 73, 67, -94, 19, -102, 82, 114,
> 100, -66, -22, 79, -51, -107, -73, 64, -36, -72, -42, -103]
> 2023-06-28 09:40:24,594 WARN
> org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
> java.lang.NullPointerException
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457)
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150)
> at
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966)
> at
> org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294)
> at
> org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267)
> {code}
> Same behaviour is there even after 5 minutes which is the default ambari
> metrics metadata sync interval.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[
https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751688#comment-17751688
]
Mohammad Arshad commented on AMBARI-25984:
--
After fix Daily aggregate information is included in summary API response.
!screenshot-1.png!
> Ambari metrics summary API missing daily aggregator info
>
>
> Key: AMBARI-25984
> URL: https://issues.apache.org/jira/browse/AMBARI-25984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
> {noformat}
> {
> "timestamp": 1691405233095,
> "metadata": {
> "timeline_metric_store_watcher": "2",
> "datanode": "329",
> "HOST": "154",
> "jobhistoryserver": "67",
> "namenode": "457",
> "ambari_server": "79",
> "hiveserver2": "116",
> "amssmoketestfake": "2",
> "hivemetastore": "438",
> "resourcemanager": "257",
> "Number of Hosts": "7",
> "applicationhistoryserver": "108",
> "nodemanager": "366",
> "hbase": "1950",
> "ams-hbase": "5583"
> },
> "aggregation": {
> "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
> "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
> "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
> }
> }
> {noformat}
> In above aggregation information TimelineMetricHostAggregatorDaily and
> TimelineClusterAggregatorDaily are missing. Summary API should return these
> aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[
https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25984:
-
Attachment: screenshot-1.png
> Ambari metrics summary API missing daily aggregator info
>
>
> Key: AMBARI-25984
> URL: https://issues.apache.org/jira/browse/AMBARI-25984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
> {noformat}
> {
> "timestamp": 1691405233095,
> "metadata": {
> "timeline_metric_store_watcher": "2",
> "datanode": "329",
> "HOST": "154",
> "jobhistoryserver": "67",
> "namenode": "457",
> "ambari_server": "79",
> "hiveserver2": "116",
> "amssmoketestfake": "2",
> "hivemetastore": "438",
> "resourcemanager": "257",
> "Number of Hosts": "7",
> "applicationhistoryserver": "108",
> "nodemanager": "366",
> "hbase": "1950",
> "ams-hbase": "5583"
> },
> "aggregation": {
> "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
> "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
> "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
> }
> }
> {noformat}
> In above aggregation information TimelineMetricHostAggregatorDaily and
> TimelineClusterAggregatorDaily are missing. Summary API should return these
> aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
Mohammad Arshad created AMBARI-25984:
Summary: Ambari metrics summary API missing daily aggregator info
Key: AMBARI-25984
URL: https://issues.apache.org/jira/browse/AMBARI-25984
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
{noformat}
{
"timestamp": 1691405233095,
"metadata": {
"timeline_metric_store_watcher": "2",
"datanode": "329",
"HOST": "154",
"jobhistoryserver": "67",
"namenode": "457",
"ambari_server": "79",
"hiveserver2": "116",
"amssmoketestfake": "2",
"hivemetastore": "438",
"resourcemanager": "257",
"Number of Hosts": "7",
"applicationhistoryserver": "108",
"nodemanager": "366",
"hbase": "1950",
"ams-hbase": "5583"
},
"aggregation": {
"TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
"TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
"TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
"TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
"TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
}
}
{noformat}
In above aggregation information TimelineMetricHostAggregatorDaily and
TimelineClusterAggregatorDaily are missing. Summary API should return these
aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751362#comment-17751362
]
Mohammad Arshad commented on AMBARI-25974:
--
!image-2023-08-06-12-52-53-828.png!
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Attachments: image-2023-08-06-12-52-53-828.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25974:
-
Attachment: image-2023-08-06-12-52-53-828.png
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Attachments: image-2023-08-06-12-52-53-828.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751361#comment-17751361
]
Mohammad Arshad commented on AMBARI-25974:
--
Removed ambari-infra and ambari-logsearch test execution from Ambari Pull
Request Builder CI
Removed following scripts:
{noformat}
stage('Ambari Infra Tests') {
steps {
script{
def dirExists = fileExists 'ambari-infra'
if (dirExists) {
dir('ambari-infra') {
sh 'mvn -am test -Dmaven.artifact.threads=10 -Drat.skip'
}
}
}
}
}
stage('Ambari LogSearch Tests') {
steps {
script{
def dirExists = fileExists 'ambari-logsearch'
if (dirExists) {
dir('ambari-logsearch') {
sh 'mvn -am test -Dmaven.artifact.threads=10 -Drat.skip'
}
}
}
}
}
{noformat}
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Attachments: image-2023-08-06-12-52-53-828.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751359#comment-17751359
]
Mohammad Arshad commented on AMBARI-25974:
--
In trunk, Ambari-infra and ambari-logsearch has long been moved to separate
repositories https://github.com/apache/ambari-infra and
https://github.com/apache/ambari-logsearch
There is no change from long time in these two modules in branch-2 code as
well. I think we can remove these module test execution from Ambari Pull
Request Builder CI
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Comment Edited] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750717#comment-17750717
]
Mohammad Arshad edited comment on AMBARI-25974 at 8/3/23 12:12 PM:
---
branch-2.7 infra and logsearch test builds started failing again, but with some
other error this time
Ambari infra Test build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-infra-solr-plugin: Could not
resolve dependencies for project
org.apache.ambari:ambari-infra-solr-plugin:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Ambari logsearch test build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-logsearch-it: Could not
resolve dependencies for project
org.apache.ambari:ambari-logsearch-it:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Any idea how to handle this?
Shall we add parameter, in these two module build scripts, to skip the cert
validation ?
was (Author: arshad.mohammad):
branch-2.7 infra and logsearch builds started failing again, but with some
other error this time
Ambari infra build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-infra-solr-plugin: Could not
resolve dependencies for project
org.apache.ambari:ambari-infra-solr-plugin:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Ambari logsearch build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-logsearch-it: Could not
resolve dependencies for project
org.apache.ambari:ambari-logsearch-it:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Any idea how to handle this?
Shall we add parameter, in these two module build scripts, to skip the cert
validation ?
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750717#comment-17750717
]
Mohammad Arshad commented on AMBARI-25974:
--
branch-2.7 infra and logsearch builds started failing again, but with some
other error this time
Ambari infra build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-infra-solr-plugin: Could not
resolve dependencies for project
org.apache.ambari:ambari-infra-solr-plugin:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Ambari logsearch build is failing with error:
{code:java}
[ERROR] Failed to execute goal on project ambari-logsearch-it: Could not
resolve dependencies for project
org.apache.ambari:ambari-logsearch-it:jar:2.7.8.0.0: Failed to collect
dependencies at org.apache.solr:solr-core:jar:7.7.3 ->
org.restlet.jee:org.restlet:jar:2.3.0: Failed to read artifact descriptor for
org.restlet.jee:org.restlet:jar:2.3.0: The following artifacts could not be
resolved: org.restlet.jee:org.restlet:pom:2.3.0 (absent): Could not transfer
artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(https://maven.restlet.com): PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed: NotAfter:
Sun Nov 13 17:05:56 UTC 2022 -> [Help 1]
{code}
Any idea how to handle this?
Shall we add parameter, in these two module build scripts, to skip the cert
validation ?
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
>
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747446#comment-17747446
]
Mohammad Arshad commented on AMBARI-25974:
--
Thanks [~wzhy] for this valuable information.
Raised the PR as you suggested. Build is successful now.
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25976) Upgrade grafana to remediate CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747445#comment-17747445 ] Mohammad Arshad commented on AMBARI-25976: -- I test ambari trunk with BIGTOP 3.2.0 stack. As bigtop 3.2.0 is available for download it is easy to test ambari trunk. How can we test ambari branch-2.7, from where we can get the HDP stack 2.6 to test ambari branch-2.7 ? > Upgrade grafana to remediate CVEs > - > > Key: AMBARI-25976 > URL: https://issues.apache.org/jira/browse/AMBARI-25976 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.1.0 > > > Grafana Security Advisory > https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ > Upgrade grafana to latest 9.x available version 9.5.6 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[ https://issues.apache.org/jira/browse/AMBARI-25974 ]
Mohammad Arshad deleted comment on AMBARI-25974:
--
was (Author: arshad.mohammad):
Thanks [~wzhy] for sharing this useful information.
To resolve the compilation issue added backtype.storm.metric.IClusterReporter
interface in ambari-metrics-storm-sink-legacy. Shall we do this way? Lets
remove the dependency from hortonworks repository.
Raised PR https://github.com/apache/ambari/pull/3730
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747424#comment-17747424
]
Mohammad Arshad commented on AMBARI-25974:
--
Thanks [~wzhy] for sharing this useful information.
To resolve the compilation issue added backtype.storm.metric.IClusterReporter
interface in ambari-metrics-storm-sink-legacy. Shall we do this way? Lets
remove the dependency from hortonworks repository.
Raised PR https://github.com/apache/ambari/pull/3730
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747312#comment-17747312
]
Mohammad Arshad commented on AMBARI-25974:
--
To fix the compilation error changed zookeeper version from 3.4.6.2.3.0.0-2557
to 3.4.6 and changed storm version from 0.10.0.2.3.0.0-2557 to 0.10.0
Deleted https://repo.hortonworks.com/content/groups/public repo references
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747314#comment-17747314
]
Mohammad Arshad commented on AMBARI-25974:
--
ambari-metrics-storm-sink-legacy project compilation error is not getting
resolved.
0.10.0.2.3.0.0-2557 version is not available. Changing to 0.10.0 is throwing
following error
{noformat}
[ERROR] symbol: class IClusterReporter
ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java:37:29
java: cannot find symbol
symbol: class IClusterReporter
location: package backtype.storm.metric{noformat}
Making code changes to adapt new version changes is not much useful as same
thing is already done in ambari-metrics-storm-sink project.
any idea how to move forward? can we delete ambari-metrics-storm-sink-legacy
project?
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25974) branch-2.7 metrics,infra and logsearch builds are failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25974:
-
Summary: branch-2.7 metrics,infra and logsearch builds are failing because
few dependencies are not available (was: branch-2.7 metrics,infra and
logsearch build is failing because few dependencies are not available)
> branch-2.7 metrics,infra and logsearch builds are failing because few
> dependencies are not available
>
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25974) branch-2.7 metrics,infra and logsearch build is failing because few dependencies are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25974:
-
Summary: branch-2.7 metrics,infra and logsearch build is failing because
few dependencies are not available (was: Branch-2.7 metrics build is failing
because some dependency versions are not available)
> branch-2.7 metrics,infra and logsearch build is failing because few
> dependencies are not available
> --
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25974) Branch-2.7 metrics build is failing because some dependency versions are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747285#comment-17747285
]
Mohammad Arshad commented on AMBARI-25974:
--
Compilation is failing because zookeeper 3.4.6.2.3.0.0-2557 and storm
0.10.0.2.3.0.0-2557 is no more available in hortonworks repository
https://repo.hortonworks.com/content/groups/public
> Branch-2.7 metrics build is failing because some dependency versions are not
> available
> --
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
[
https://issues.apache.org/jira/browse/AMBARI-25977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747022#comment-17747022
]
Mohammad Arshad commented on AMBARI-25977:
--
After fix, by default phoenix.mutate.maxSizeBytes is configured to 267386880
!screenshot-1.png!
> Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
> ---
>
> Key: AMBARI-25977
> URL: https://issues.apache.org/jira/browse/AMBARI-25977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number
> of records in a batch by default are set to 1, some times this value is
> not sufficient and collector fails, to store aggregated data, with following
> error
> {code:java}
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858209
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
> 1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
> 1690284122957=133.09041926456285}
> 2023-07-25 11:21:21,597 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858964
> 2023-07-25 11:21:21,598 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
> 1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
> 1690284122957=195.3577965382318}
> {code}
> lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
> more reasonable with batch size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
[
https://issues.apache.org/jira/browse/AMBARI-25977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25977:
-
Attachment: screenshot-1.png
> Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
> ---
>
> Key: AMBARI-25977
> URL: https://issues.apache.org/jira/browse/AMBARI-25977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number
> of records in a batch by default are set to 1, some times this value is
> not sufficient and collector fails, to store aggregated data, with following
> error
> {code:java}
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858209
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
> 1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
> 1690284122957=133.09041926456285}
> 2023-07-25 11:21:21,597 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858964
> 2023-07-25 11:21:21,598 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
> 1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
> 1690284122957=195.3577965382318}
> {code}
> lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
> more reasonable with batch size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25976) Upgrade grafana to remediate CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746957#comment-17746957 ] Mohammad Arshad commented on AMBARI-25976: -- Thanks [~brahmareddy] for your review. Currently branch-2.7 is using grafana 6.x. We have to backport many jiras to upgrade to grafana 9.x. I will raise separate jira to address branch-2.7 grafana upgrade. > Upgrade grafana to remediate CVEs > - > > Key: AMBARI-25976 > URL: https://issues.apache.org/jira/browse/AMBARI-25976 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > Grafana Security Advisory > https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ > Upgrade grafana to latest 9.x available version 9.5.6 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
Mohammad Arshad created AMBARI-25977:
Summary: Increase default value of phoenix.mutate.maxSizeBytes
from 100 MB to 255 MB
Key: AMBARI-25977
URL: https://issues.apache.org/jira/browse/AMBARI-25977
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number of
records in a batch by default are set to 1, some times this value is not
sufficient and collector fails, to store aggregated data, with following error
{code:java}
2023-07-25 11:21:21,500 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on insert
records to store : ERROR 730 (LIM02): MutationState size is bigger than maximum
allowed number of bytes, try upserting rows in smaller batches or using
autocommit on for deletes. maxMutationSizeBytes=104857600
mutationSizeBytes=104858209
2023-07-25 11:21:21,500 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
cannot be stored :
[regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
1690284122957=133.09041926456285}
2023-07-25 11:21:21,597 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on insert
records to store : ERROR 730 (LIM02): MutationState size is bigger than maximum
allowed number of bytes, try upserting rows in smaller batches or using
autocommit on for deletes. maxMutationSizeBytes=104857600
mutationSizeBytes=104858964
2023-07-25 11:21:21,598 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
cannot be stored :
[regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
1690284122957=195.3577965382318}
{code}
lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
more reasonable with batch size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-3.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png, screenshot-3.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746909#comment-17746909
]
Mohammad Arshad commented on AMBARI-25975:
--
After fix dashboards are displaying data properly
!screenshot-1.png!
!screenshot-2.png!
!screenshot-3.png!
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png, screenshot-3.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-2.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-1.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25976) Upgrade grafana to remediate CVEs
Mohammad Arshad created AMBARI-25976: Summary: Upgrade grafana to remediate CVEs Key: AMBARI-25976 URL: https://issues.apache.org/jira/browse/AMBARI-25976 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Grafana Security Advisory https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ Upgrade grafana to latest 9.x available version 9.5.6 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
