[jira] [Updated] (AMBARI-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25876: Labels: pull-request-available (was: ) > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- 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-25878) Fix TopologyManagerTest after merging AMBARI-25186
[
https://issues.apache.org/jira/browse/AMBARI-25878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25878:
---
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix TopologyManagerTest after merging AMBARI-25186
> --
>
> Key: AMBARI-25878
> URL: https://issues.apache.org/jira/browse/AMBARI-25878
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, TopologyManagerTest fails with the following errors.
> {code}
> $ $ mvn clean test -Dtest=TopologyManagerTest -f ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.server.topology.TopologyManagerTest
> [ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
> 2.226 s <<< FAILURE! - in
> org.apache.ambari.server.topology.TopologyManagerTest
> [ERROR]
> testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(org.apache.ambari.server.topology.TopologyManagerTest)
> Time elapsed: 0.016 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(TopologyManagerTest.java:498)
> [ERROR]
> testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(org.apache.ambari.server.topology.TopologyManagerTest)
> Time elapsed: 0.011 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(TopologyManagerTest.java:524)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
> TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone:498
> » NullPointer
> [ERROR]
> TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity:524
> » NullPointer
> [INFO]
> [ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 45.849 s
> [INFO] Finished at: 2023-02-28T10:41:59+09:00
> [INFO]
>
> {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-25877) Fix test configuration files used by ServicePropertiesTest
[
https://issues.apache.org/jira/browse/AMBARI-25877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25877:
---
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix test configuration files used by ServicePropertiesTest
> --
>
> Key: AMBARI-25877
> URL: https://issues.apache.org/jira/browse/AMBARI-25877
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, ServicePropertiesTest fails because some of configuration files
> are incomplete or invalid. For example:
> {code}
> $ mvn clean test -Dtest=ServicePropertiesTest -f ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.server.state.ServicePropertiesTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.198
> s <<< FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> [ERROR]
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 0.183 s <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/sekikn/repos/ambari/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/BIGTOP/3.2.0/services/HIVE/configuration/hive-site.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, supported-refresh-commands,
> on-stack-upgrade, property-type, value-attributes, depends-on,
> property_depended_by, used-by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:51)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] ServicePropertiesTest.validatePropertySchemaOfServiceXMLs:51 »
> Ambari File /ho...
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.233 s
> [INFO] Finished at: 2023-02-28T10:28:45+09:00
> [INFO]
>
> {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-25874) Fix AlertTargetResourceProviderTest to work after merging AMBARI-25300
[
https://issues.apache.org/jira/browse/AMBARI-25874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25874:
---
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix AlertTargetResourceProviderTest to work after merging AMBARI-25300
> --
>
> Key: AMBARI-25874
> URL: https://issues.apache.org/jira/browse/AMBARI-25874
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, running the following test fails:
> {code}
> $ mvn clean test -Dtest="AlertTargetResourceProviderTest#testEnable" -f
> ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.173
> s <<< FAILURE! - in
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
> [ERROR]
> testEnable(org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest)
> Time elapsed: 3.112 s <<< FAILURE!
> java.lang.AssertionError:
> Unexpected method call AlertDispatchDAO.findTargetByName("The
> Administrators"):
> AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
> actual: 0
> at
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest.testEnable(AlertTargetResourceProviderTest.java:1095)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] AlertTargetResourceProviderTest.testEnable:1095
> Unexpected method call AlertDispatchDAO.findTargetByName("The
> Administrators"):
> AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
> actual: 0
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 03:04 min
> [INFO] Finished at: 2023-02-28T00:18:38+09:00
> [INFO]
>
> {code}
> This is because AMBARI-25300 changed
> {{AlertTargetResourceProvider#createAlertTargets}} to always (except for the
> cases of exception) call {{AlertDispatchDAO#findTargetByName}}
>
> (https://github.com/apache/ambari/commit/05c826ec1a0eb2d672ad84505d9bde95a578fa09#diff-fff060a3bbe1aa6b1fd811d058ba8005333f8422dc6b4de92e133c4e2988f000),
> but the corresponding mock in {{AlertTargetResourceProviderTest#testEnable}}
> doesn't have a defined behavior for that method.
--
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-25871) When I add hive metastore, why should I restart unrelated services
[ https://issues.apache.org/jira/browse/AMBARI-25871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694301#comment-17694301 ] LiJie2023 commented on AMBARI-25871: [~wuzhiguo] > When I add hive metastore, why should I restart unrelated services > -- > > Key: AMBARI-25871 > URL: https://issues.apache.org/jira/browse/AMBARI-25871 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: LiJie2023 >Priority: Major > Labels: features, patch > Attachments: image-2023-02-27-11-01-19-420.png, > image-2023-02-27-11-01-44-372.png > > > 1. Add hive metastore > !image-2023-02-27-11-01-19-420.png! > > 2. Restart unrelated services, such as spark > !image-2023-02-27-11-01-44-372.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-25873) When I do NameNode HA, I don't want to stop all services
[ https://issues.apache.org/jira/browse/AMBARI-25873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694300#comment-17694300 ] LiJie2023 commented on AMBARI-25873: [~wuzhiguo] > When I do NameNode HA, I don't want to stop all services > > > Key: AMBARI-25873 > URL: https://issues.apache.org/jira/browse/AMBARI-25873 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.5 >Reporter: LiJie2023 >Priority: Blocker > Labels: easyfix, pull-request-available > Attachments: image-2023-02-27-22-07-06-192.png, > image-2023-02-27-22-07-20-143.png > > > When I do NameNode HA, I need to stop all services, but I have customized > some services that do not depend on hdfs. At this time, I do not need to > stop. What should I do? Is there any relevant code that can be modified here > > !image-2023-02-27-22-07-06-192.png! > > > !image-2023-02-27-22-07-20-143.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-25878) Fix TopologyManagerTest after merging AMBARI-25186
[
https://issues.apache.org/jira/browse/AMBARI-25878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kengo Seki updated AMBARI-25878:
Status: Patch Available (was: Open)
> Fix TopologyManagerTest after merging AMBARI-25186
> --
>
> Key: AMBARI-25878
> URL: https://issues.apache.org/jira/browse/AMBARI-25878
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, TopologyManagerTest fails with the following errors.
> {code}
> $ $ mvn clean test -Dtest=TopologyManagerTest -f ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.server.topology.TopologyManagerTest
> [ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
> 2.226 s <<< FAILURE! - in
> org.apache.ambari.server.topology.TopologyManagerTest
> [ERROR]
> testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(org.apache.ambari.server.topology.TopologyManagerTest)
> Time elapsed: 0.016 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(TopologyManagerTest.java:498)
> [ERROR]
> testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(org.apache.ambari.server.topology.TopologyManagerTest)
> Time elapsed: 0.011 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(TopologyManagerTest.java:524)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
> TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone:498
> » NullPointer
> [ERROR]
> TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity:524
> » NullPointer
> [INFO]
> [ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 45.849 s
> [INFO] Finished at: 2023-02-28T10:41:59+09:00
> [INFO]
>
> {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-25878) Fix TopologyManagerTest after merging AMBARI-25186
Kengo Seki created AMBARI-25878:
---
Summary: Fix TopologyManagerTest after merging AMBARI-25186
Key: AMBARI-25878
URL: https://issues.apache.org/jira/browse/AMBARI-25878
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Kengo Seki
Assignee: Kengo Seki
Currently, TopologyManagerTest fails with the following errors.
{code}
$ $ mvn clean test -Dtest=TopologyManagerTest -f ambari-server/pom.xml
...
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.ambari.server.topology.TopologyManagerTest
[ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.226
s <<< FAILURE! - in org.apache.ambari.server.topology.TopologyManagerTest
[ERROR]
testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(org.apache.ambari.server.topology.TopologyManagerTest)
Time elapsed: 0.016 s <<< ERROR!
java.lang.NullPointerException
at
org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone(TopologyManagerTest.java:498)
[ERROR]
testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(org.apache.ambari.server.topology.TopologyManagerTest)
Time elapsed: 0.011 s <<< ERROR!
java.lang.NullPointerException
at
org.apache.ambari.server.topology.TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity(TopologyManagerTest.java:524)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]
TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_KdcTypeNone:498 »
NullPointer
[ERROR]
TopologyManagerTest.testDoNotAddKerberosClientAtTopologyInit_ManageIdentity:524
» NullPointer
[INFO]
[ERROR] Tests run: 13, Failures: 0, Errors: 2, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 45.849 s
[INFO] Finished at: 2023-02-28T10:41:59+09:00
[INFO]
{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-25877) Fix test configuration files used by ServicePropertiesTest
[
https://issues.apache.org/jira/browse/AMBARI-25877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kengo Seki updated AMBARI-25877:
Status: Patch Available (was: Open)
> Fix test configuration files used by ServicePropertiesTest
> --
>
> Key: AMBARI-25877
> URL: https://issues.apache.org/jira/browse/AMBARI-25877
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, ServicePropertiesTest fails because some of configuration files
> are incomplete or invalid. For example:
> {code}
> $ mvn clean test -Dtest=ServicePropertiesTest -f ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.ambari.server.state.ServicePropertiesTest
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.198
> s <<< FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
> [ERROR]
> validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
> Time elapsed: 0.183 s <<< ERROR!
> org.apache.ambari.server.AmbariException: File
> /home/sekikn/repos/ambari/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/BIGTOP/3.2.0/services/HIVE/configuration/hive-site.xml
> didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
> content of element 'property' is not complete. One of '{display-name,
> filename, deleted, final, on-ambari-upgrade, supported-refresh-commands,
> on-stack-upgrade, property-type, value-attributes, depends-on,
> property_depended_by, used-by}' is expected.
> at
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:51)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] ServicePropertiesTest.validatePropertySchemaOfServiceXMLs:51 »
> Ambari File /ho...
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.233 s
> [INFO] Finished at: 2023-02-28T10:28:45+09:00
> [INFO]
>
> {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-25877) Fix test configuration files used by ServicePropertiesTest
Kengo Seki created AMBARI-25877:
---
Summary: Fix test configuration files used by ServicePropertiesTest
Key: AMBARI-25877
URL: https://issues.apache.org/jira/browse/AMBARI-25877
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Kengo Seki
Assignee: Kengo Seki
Currently, ServicePropertiesTest fails because some of configuration files are
incomplete or invalid. For example:
{code}
$ mvn clean test -Dtest=ServicePropertiesTest -f ambari-server/pom.xml
...
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.ambari.server.state.ServicePropertiesTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.198 s
<<< FAILURE! - in org.apache.ambari.server.state.ServicePropertiesTest
[ERROR]
validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
Time elapsed: 0.183 s <<< ERROR!
org.apache.ambari.server.AmbariException: File
/home/sekikn/repos/ambari/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/stacks/BIGTOP/3.2.0/services/HIVE/configuration/hive-site.xml
didn't pass the validation. Error message is : cvc-complex-type.2.4.b: The
content of element 'property' is not complete. One of '{display-name, filename,
deleted, final, on-ambari-upgrade, supported-refresh-commands,
on-stack-upgrade, property-type, value-attributes, depends-on,
property_depended_by, used-by}' is expected.
at
org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:51)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] ServicePropertiesTest.validatePropertySchemaOfServiceXMLs:51 » Ambari
File /ho...
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 40.233 s
[INFO] Finished at: 2023-02-28T10:28:45+09:00
[INFO]
{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-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694251#comment-17694251 ] Kengo Seki commented on AMBARI-25876: - 3.0.0 sounds good to me. > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- 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-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25876: --- Description: When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, and the version number contains 5 digits, x.x.x.x.x, which also contains the release version number. If we merge AMBARI-25875, then the version number will only be 3 digits and will no longer contain the release version number, I think this is a big change for identifying versions, so I prefer to upgrade the major version and set the next version to 3.0.0 for ambari-metrics. was: When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, and the version number contains 5 digits, x.x.x.x.x, which also contains the release version number. If we merge Ambari-25875, then the version number will only be 3 digits and will no longer contain the release version number, I think this is a big change for identifying versions, so I prefer to upgrade the major version and set the next version to 3.0.0 for ambari-metrics. > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- 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-25876) Define next version number for Ambari Metrics
Zhiguo Wu created AMBARI-25876: -- Summary: Define next version number for Ambari Metrics Key: AMBARI-25876 URL: https://issues.apache.org/jira/browse/AMBARI-25876 Project: Ambari Issue Type: Task Reporter: Zhiguo Wu Assignee: Zhiguo Wu When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, and the version number contains 5 digits, x.x.x.x.x, which also contains the release version number. If we merge Ambari-25875, then the version number will only be 3 digits and will no longer contain the release version number, I think this is a big change for identifying versions, so I prefer to upgrade the major version and set the next version to 3.0.0 for ambari-metrics. -- 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-25875) Use separate property for release version for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25875: Labels: pull-request-available (was: ) > Use separate property for release version for Ambari Metrics > > > Key: AMBARI-25875 > URL: https://issues.apache.org/jira/browse/AMBARI-25875 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for > release version, but this may confused for people, so I'd like to split *p* > into a separate property -- 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-25875) Use separate property for release version for Ambari Metrics
Zhiguo Wu created AMBARI-25875: -- Summary: Use separate property for release version for Ambari Metrics Key: AMBARI-25875 URL: https://issues.apache.org/jira/browse/AMBARI-25875 Project: Ambari Issue Type: Task Reporter: Zhiguo Wu Assignee: Zhiguo Wu In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for release verion, but this may confused for people, so I'd like to split *p* into a separate property -- 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-25875) Use separate property for release version for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25875: --- Description: In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for release version, but this may confused for people, so I'd like to split *p* into a separate property (was: In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for release verion, but this may confused for people, so I'd like to split *p* into a separate property) > Use separate property for release version for Ambari Metrics > > > Key: AMBARI-25875 > URL: https://issues.apache.org/jira/browse/AMBARI-25875 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > > In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for > release version, but this may confused for people, so I'd like to split *p* > into a separate property -- 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-25874) Fix AlertTargetResourceProviderTest to work after merging AMBARI-25300
[
https://issues.apache.org/jira/browse/AMBARI-25874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kengo Seki updated AMBARI-25874:
Status: Patch Available (was: Open)
> Fix AlertTargetResourceProviderTest to work after merging AMBARI-25300
> --
>
> Key: AMBARI-25874
> URL: https://issues.apache.org/jira/browse/AMBARI-25874
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, running the following test fails:
> {code}
> $ mvn clean test -Dtest="AlertTargetResourceProviderTest#testEnable" -f
> ambari-server/pom.xml
> ...
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.173
> s <<< FAILURE! - in
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
> [ERROR]
> testEnable(org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest)
> Time elapsed: 3.112 s <<< FAILURE!
> java.lang.AssertionError:
> Unexpected method call AlertDispatchDAO.findTargetByName("The
> Administrators"):
> AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
> actual: 0
> at
> org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest.testEnable(AlertTargetResourceProviderTest.java:1095)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] AlertTargetResourceProviderTest.testEnable:1095
> Unexpected method call AlertDispatchDAO.findTargetByName("The
> Administrators"):
> AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
> actual: 0
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 03:04 min
> [INFO] Finished at: 2023-02-28T00:18:38+09:00
> [INFO]
>
> {code}
> This is because AMBARI-25300 changed
> {{AlertTargetResourceProvider#createAlertTargets}} to always (except for the
> cases of exception) call {{AlertDispatchDAO#findTargetByName}}
>
> (https://github.com/apache/ambari/commit/05c826ec1a0eb2d672ad84505d9bde95a578fa09#diff-fff060a3bbe1aa6b1fd811d058ba8005333f8422dc6b4de92e133c4e2988f000),
> but the corresponding mock in {{AlertTargetResourceProviderTest#testEnable}}
> doesn't have a defined behavior for that method.
--
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-25874) Fix AlertTargetResourceProviderTest to work after merging AMBARI-25300
Kengo Seki created AMBARI-25874:
---
Summary: Fix AlertTargetResourceProviderTest to work after merging
AMBARI-25300
Key: AMBARI-25874
URL: https://issues.apache.org/jira/browse/AMBARI-25874
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Kengo Seki
Assignee: Kengo Seki
Currently, running the following test fails:
{code}
$ mvn clean test -Dtest="AlertTargetResourceProviderTest#testEnable" -f
ambari-server/pom.xml
...
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.173 s
<<< FAILURE! - in
org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest
[ERROR]
testEnable(org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest)
Time elapsed: 3.112 s <<< FAILURE!
java.lang.AssertionError:
Unexpected method call AlertDispatchDAO.findTargetByName("The
Administrators"):
AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
actual: 0
at
org.apache.ambari.server.controller.internal.AlertTargetResourceProviderTest.testEnable(AlertTargetResourceProviderTest.java:1095)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] AlertTargetResourceProviderTest.testEnable:1095
Unexpected method call AlertDispatchDAO.findTargetByName("The
Administrators"):
AlertDispatchDAO.create(capture(Nothing captured yet)): expected: 1,
actual: 0
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 03:04 min
[INFO] Finished at: 2023-02-28T00:18:38+09:00
[INFO]
{code}
This is because AMBARI-25300 changed
{{AlertTargetResourceProvider#createAlertTargets}} to always (except for the
cases of exception) call {{AlertDispatchDAO#findTargetByName}}
(https://github.com/apache/ambari/commit/05c826ec1a0eb2d672ad84505d9bde95a578fa09#diff-fff060a3bbe1aa6b1fd811d058ba8005333f8422dc6b4de92e133c4e2988f000),
but the corresponding mock in {{AlertTargetResourceProviderTest#testEnable}}
doesn't have a defined behavior for that method.
--
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-25871) When I add hive metastore, why should I restart unrelated services
[ https://issues.apache.org/jira/browse/AMBARI-25871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694047#comment-17694047 ] LiJie2023 commented on AMBARI-25871: I don't know how to deal with it. Can you help me solve it > When I add hive metastore, why should I restart unrelated services > -- > > Key: AMBARI-25871 > URL: https://issues.apache.org/jira/browse/AMBARI-25871 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: LiJie2023 >Priority: Major > Labels: features, patch > Attachments: image-2023-02-27-11-01-19-420.png, > image-2023-02-27-11-01-44-372.png > > > 1. Add hive metastore > !image-2023-02-27-11-01-19-420.png! > > 2. Restart unrelated services, such as spark > !image-2023-02-27-11-01-44-372.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-25873) When I do NameNode HA, I don't want to stop all services
[ https://issues.apache.org/jira/browse/AMBARI-25873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694046#comment-17694046 ] LiJie2023 commented on AMBARI-25873: I don't know how to deal with it. Can you help me solve it > When I do NameNode HA, I don't want to stop all services > > > Key: AMBARI-25873 > URL: https://issues.apache.org/jira/browse/AMBARI-25873 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.5 >Reporter: LiJie2023 >Priority: Blocker > Labels: easyfix, pull-request-available > Attachments: image-2023-02-27-22-07-06-192.png, > image-2023-02-27-22-07-20-143.png > > > When I do NameNode HA, I need to stop all services, but I have customized > some services that do not depend on hdfs. At this time, I do not need to > stop. What should I do? Is there any relevant code that can be modified here > > !image-2023-02-27-22-07-06-192.png! > > > !image-2023-02-27-22-07-20-143.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-25873) When I do NameNode HA, I don't want to stop all services
LiJie2023 created AMBARI-25873: -- Summary: When I do NameNode HA, I don't want to stop all services Key: AMBARI-25873 URL: https://issues.apache.org/jira/browse/AMBARI-25873 Project: Ambari Issue Type: Improvement Affects Versions: 2.7.5 Reporter: LiJie2023 Attachments: image-2023-02-27-22-07-06-192.png, image-2023-02-27-22-07-20-143.png When I do NameNode HA, I need to stop all services, but I have customized some services that do not depend on hdfs. At this time, I do not need to stop. What should I do? Is there any relevant code that can be modified here !image-2023-02-27-22-07-06-192.png! !image-2023-02-27-22-07-20-143.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-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693918#comment-17693918
]
Mohammad Arshad commented on AMBARI-25803:
--
yes
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above command logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-25870) Upgrade Swagger to 1.6.2+ for avoiding NoSuchMethodError
[
https://issues.apache.org/jira/browse/AMBARI-25870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25870:
---
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade Swagger to 1.6.2+ for avoiding NoSuchMethodError
>
>
> Key: AMBARI-25870
> URL: https://issues.apache.org/jira/browse/AMBARI-25870
> Project: Ambari
> Issue Type: Bug
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, running unit tests for ambari-utility fails with the following
> error.
> {code}
> $ mvn clean test -f ambari-utility/pom.xml
> ...
> [ERROR] Tests run: 8, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.656
> s <<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest
> ...
> [ERROR] Errors:
> [ERROR]
> AmbariSwaggerReaderTest.swaggerApiThatIsBothTopLevelAndNestedIsCountedAsTopLevel:171
> » NoSuchMethod
> [ERROR] AmbariSwaggerReaderTest.swaggerBasicCase:71 » NoSuchMethod
> com.fasterxml.jacks...
> [ERROR] AmbariSwaggerReaderTest.swaggerConflictingNestedApis:86 »
> NoSuchMethod com.fas...
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithBadPreferredParent:140
> » NoSuchMethod
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithPreferredParent:103 »
> NoSuchMethod
> [ERROR]
> AmbariSwaggerReaderTest.swaggerConflictingNestedApisWithSamePreferredParent:121
> » NoSuchMethod
> [ERROR] AmbariSwaggerReaderTest.swaggerNestedApisWithOverwrite:156 »
> NoSuchMethod com
> [INFO]
> [ERROR] Tests run: 10, Failures: 0, Errors: 7, Skipped: 1
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> {code}
> This is because the old version of Swagger uses Jackson's {{getType}} method
> internally, [which is deprecated and removed in
> v2.9|https://fasterxml.github.io/jackson-databind/javadoc/2.8/com/fasterxml/jackson/databind/introspect/Annotated.html#getType(com.fasterxml.jackson.databind.type.TypeBindings)],
> while [we are using Jackson
> v2.12|https://github.com/apache/ambari/blob/trunk/ambari-project/pom.xml#L44-L45].
> Upgrading Swagger to 1.6.2 or greater fixes this problem, just like the
> following case.
> https://github.com/swagger-api/swagger-core/issues/3554#issuecomment-652366376
--
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-25869) Upgrade TestContainers for fixing functional tests
[
https://issues.apache.org/jira/browse/AMBARI-25869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25869:
---
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Upgrade TestContainers for fixing functional tests
> --
>
> Key: AMBARI-25869
> URL: https://issues.apache.org/jira/browse/AMBARI-25869
> Project: Ambari
> Issue Type: Improvement
> Components: test
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, running functional tests fails with the following error:
> {code}
> $ mvn clean verify -f ambari-funtest/pom.xml
> ...
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 8.064
> s <<< FAILURE! - in org.apache.ambari.funtest.server.tests.db.DDLCreateIT
> [ERROR] mysql(org.apache.ambari.funtest.server.tests.db.DDLCreateIT) Time
> elapsed: 0.842 s <<< ERROR!
> com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: quay.io/testcontainers/ryuk:0.2.2"}
> at
> org.apache.ambari.funtest.server.tests.db.DDLCreateIT.lambda$mysql$0(DDLCreateIT.java:42)
> at
> org.apache.ambari.funtest.server.tests.db.DDLCreateIT.testSchemaCreate(DDLCreateIT.java:53)
> at
> org.apache.ambari.funtest.server.tests.db.DDLCreateIT.mysql(DDLCreateIT.java:42)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] DDLCreateIT.mysql:42->testSchemaCreate:53->lambda$mysql$0:42 »
> NotFound {"mess...
> [INFO]
> [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 3
> [INFO]
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.20:verify (run-verify) @ ambari-funtest ---
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 13.497 s
> [INFO] Finished at: 2023-02-25T20:14:53+09:00
> [INFO]
>
> {code}
> Upgrading TestContainers to recent version fixes this problem.
--
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
