[jira] [Created] (AMBARI-24455) Spark service check failure after UI Deploy - non Secure with Ranger/KMS
Srikanth Janardhan created AMBARI-24455:
---
Summary: Spark service check failure after UI Deploy - non Secure
with Ranger/KMS
Key: AMBARI-24455
URL: https://issues.apache.org/jira/browse/AMBARI-24455
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Srikanth Janardhan
Fix For: 2.7.1
Spark Service check fails while UI Deploy:
{code}
stderr:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 78, in service_check
Execute(cmd, user=params.smoke_user, path=[beeline_cmd],
timeout=CHECK_COMMAND_TIMEOUT_DEFAULT)
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 314,
in _call
raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of '! /usr/hdp/current/spark2-client/bin/beeline -u
'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused'
-e 'Invalid URL' -e 'Error: Could not open'' returned 1. Hortonworks
#
This is MOTD message, added for testing in qe infra
Error: Could not open client transport with JDBC Uri:
jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
java.net.ConnectException: Connection refused (Connection refused)
(state=08S01,code=0)
Error: Could not open client transport with JDBC Uri:
jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
java.net.ConnectException: Connection refused (Connection refused)
(state=08S01,code=0)
The above exception was the cause of the following exception:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 88, in
SparkServiceCheck().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 85, in service_check
raise Fail("Connection to all Spark thrift servers servers failed")
resource_management.core.exceptions.Fail: Connection to all Spark thrift
servers servers failed
stdout:
2018-08-10 05:22:29,576 - Using hadoop conf dir: /usr/hdp/3.0.1.0-73/hadoop/conf
2018-08-10 05:22:29,600 - Execute['curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k
http://ctr-e138-1518143905142-432870-01-04.hwx.site:18081 | grep 200']
{'logoutput': True, 'tries': 5, 'user': 'ambari-qa', 'try_sleep': 3}
Hortonworks #
This is MOTD message, added for testing in qe infra
200
2018-08-10 05:22:29,794 - Execute['curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k
http://ctr-e138-1518143905142-432870-01-04.hwx.site:8999/sessions | grep
200'] {'logoutput': True, 'tries': 3, 'user': 'ambari-qa', 'try_sleep': 1}
Hortonworks #
This is MOTD message, added for testing in qe infra
200
2018-08-10 05:22:29,843 - Execute['! /usr/hdp/current/spark2-client/bin/beeline
-u
'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused'
-e 'Invalid URL' -e 'Error: Could not open''] {'path':
[u'/usr/hdp/current/spark2-client/bin/beeline'], 'user': 'ambari-qa',
'timeout': 60.0}
Command failed after 1 tries
{code}
I checked the schedule of commands and observed that Spark Thrift server start
is scheduled to run after Spark2 service check is executed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24452) [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
[
https://issues.apache.org/jira/browse/AMBARI-24452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575635#comment-16575635
]
Hudson commented on AMBARI-24452:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9784 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9784/])
[AMBARI-24452] [UI Deploy] LLAP queue is not created/set in YARN conf… (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=40aac8240bb516cf1048afd0642e1e7d6dc2027f])
* (edit) ambari-web/app/mixins/common/configs/config_recommendation_parser.js
> [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
>
>
> Key: AMBARI-24452
> URL: https://issues.apache.org/jira/browse/AMBARI-24452
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In a cluster installed via UI deploy:
> HSI was enabled as part of UI install wizard, but in the YARN configs, the
> 'llap' queue is not added leading to deploy failures. (Hive Server
> Interactive did not start)
> {code:java}
> Failed: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> java.lang.RuntimeException: org.apache.hadoop.yarn.exceptions.YarnException:
> Failed to submit application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:154)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:602)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
> Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:304)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:837)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:365)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionLaunch(ServiceClient.java:351)
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:149)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24454) WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
[ https://issues.apache.org/jira/browse/AMBARI-24454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24454: Labels: pull-request-available (was: ) > WebHdfs calls being made from containers to NameNode hosted on bare metal > host fails > > > Key: AMBARI-24454 > URL: https://issues.apache.org/jira/browse/AMBARI-24454 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575543#comment-16575543
]
Hudson commented on AMBARI-24447:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #136 (See
[https://builds.apache.org/job/Ambari-branch-2.7/136/])
[AMBARI-24447] No subject alternative DNS name exception encountered (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2df042144662f26faf256484e30f2059d2ab89ce])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/InternalSSLSocketFactory.java
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off
> --
>
> Key: AMBARI-24447
> URL: https://issues.apache.org/jira/browse/AMBARI-24447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off.
> {noformat}
> 2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
> ADKerberosOperationHandler:471 - Failed to communicate with the Active
> Directory at ldaps://adserver.example.com:636: adserver.example.com:636
> javax.naming.CommunicationException: adserver.example.com:636 [Root exception
> is javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.]
> at com.sun.jndi.ldap.Connection.(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
> ...
> Caused by: javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
> ...
> Caused by: java.security.cert.CertificateException: No subject alternative
> DNS name matching adserver.example.com found.
> at
> sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
> at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
> at
> sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
> {noformat}
> Note: This occurs when the hostname embedded in the SSL certificate does not
> match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
> used. This is not seen when Oracle JDK is used.
> {noformat:title=Observed with this version of JDK}
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
> {noformat}
> {noformat:title=Not observed with this version of JDK}
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> {noformat}
> *Solution*
> The
> {{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
> class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
> nothing in the additional overridden methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24454) WebHdfs calls being made from containers to NameNode hosted on bare metal host fails
Jaimin Jetly created AMBARI-24454: - Summary: WebHdfs calls being made from containers to NameNode hosted on bare metal host fails Key: AMBARI-24454 URL: https://issues.apache.org/jira/browse/AMBARI-24454 Project: Ambari Issue Type: Bug Components: ambari-agent Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24453) Ambari stack hook changes to create HDFS users and groups in workload cluster that has only HDFS client
[ https://issues.apache.org/jira/browse/AMBARI-24453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-24453: -- Status: Patch Available (was: Open) > Ambari stack hook changes to create HDFS users and groups in workload cluster > that has only HDFS client > --- > > Key: AMBARI-24453 > URL: https://issues.apache.org/jira/browse/AMBARI-24453 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24453) Ambari stack hook changes to create HDFS users and groups in workload cluster that has only HDFS client
[ https://issues.apache.org/jira/browse/AMBARI-24453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24453: Labels: pull-request-available (was: ) > Ambari stack hook changes to create HDFS users and groups in workload cluster > that has only HDFS client > --- > > Key: AMBARI-24453 > URL: https://issues.apache.org/jira/browse/AMBARI-24453 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24453) Ambari stack hook changes to create HDFS users and groups in workload cluster that has only HDFS client
[ https://issues.apache.org/jira/browse/AMBARI-24453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-24453: -- Summary: Ambari stack hook changes to create HDFS users and groups in workload cluster that has only HDFS client (was: Ambari stack hooks changes to create HDFS users and groups in workload cluster that has only HDFS client) > Ambari stack hook changes to create HDFS users and groups in workload cluster > that has only HDFS client > --- > > Key: AMBARI-24453 > URL: https://issues.apache.org/jira/browse/AMBARI-24453 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24452) [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
[
https://issues.apache.org/jira/browse/AMBARI-24452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24452:
Labels: pull-request-available (was: )
> [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
>
>
> Key: AMBARI-24452
> URL: https://issues.apache.org/jira/browse/AMBARI-24452
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> In a cluster installed via UI deploy:
> HSI was enabled as part of UI install wizard, but in the YARN configs, the
> 'llap' queue is not added leading to deploy failures. (Hive Server
> Interactive did not start)
> {code:java}
> Failed: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> java.lang.RuntimeException: org.apache.hadoop.yarn.exceptions.YarnException:
> Failed to submit application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:154)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:602)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
> Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
> application_1532935384747_0002 to YARN : Application
> application_1532935384747_0002 submitted by user hive to unknown queue: llap
> at
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:304)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:837)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:365)
> at
> org.apache.hadoop.yarn.service.client.ServiceClient.actionLaunch(ServiceClient.java:351)
> at
> org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:149)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24453) Ambari stack hooks changes to create HDFS users and groups in workload cluster that has only HDFS client
Jaimin Jetly created AMBARI-24453: - Summary: Ambari stack hooks changes to create HDFS users and groups in workload cluster that has only HDFS client Key: AMBARI-24453 URL: https://issues.apache.org/jira/browse/AMBARI-24453 Project: Ambari Issue Type: Bug Components: stacks Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24452) [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
Ishan Bhatt created AMBARI-24452:
Summary: [UI Deploy] LLAP queue is not created/set in YARN configs
while enabling HSI
Key: AMBARI-24452
URL: https://issues.apache.org/jira/browse/AMBARI-24452
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 2.7.1
In a cluster installed via UI deploy:
HSI was enabled as part of UI install wizard, but in the YARN configs, the
'llap' queue is not added leading to deploy failures. (Hive Server Interactive
did not start)
{code:java}
Failed: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
java.lang.RuntimeException: org.apache.hadoop.yarn.exceptions.YarnException:
Failed to submit application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
at
org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:154)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:602)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:304)
at
org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:837)
at
org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:365)
at
org.apache.hadoop.yarn.service.client.ServiceClient.actionLaunch(ServiceClient.java:351)
at
org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:149)
... 2 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575374#comment-16575374
]
Hudson commented on AMBARI-24447:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9781 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9781/])
[AMBARI-24447] No subject alternative DNS name exception encountered (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=fc6e964f5e447b1368569e455a545b8c8350cbd0])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/InternalSSLSocketFactory.java
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off
> --
>
> Key: AMBARI-24447
> URL: https://issues.apache.org/jira/browse/AMBARI-24447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off.
> {noformat}
> 2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
> ADKerberosOperationHandler:471 - Failed to communicate with the Active
> Directory at ldaps://adserver.example.com:636: adserver.example.com:636
> javax.naming.CommunicationException: adserver.example.com:636 [Root exception
> is javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.]
> at com.sun.jndi.ldap.Connection.(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
> ...
> Caused by: javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
> ...
> Caused by: java.security.cert.CertificateException: No subject alternative
> DNS name matching adserver.example.com found.
> at
> sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
> at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
> at
> sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
> {noformat}
> Note: This occurs when the hostname embedded in the SSL certificate does not
> match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
> used. This is not seen when Oracle JDK is used.
> {noformat:title=Observed with this version of JDK}
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
> {noformat}
> {noformat:title=Not observed with this version of JDK}
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> {noformat}
> *Solution*
> The
> {{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
> class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
> nothing in the additional overridden methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24447:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off
> --
>
> Key: AMBARI-24447
> URL: https://issues.apache.org/jira/browse/AMBARI-24447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off.
> {noformat}
> 2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
> ADKerberosOperationHandler:471 - Failed to communicate with the Active
> Directory at ldaps://adserver.example.com:636: adserver.example.com:636
> javax.naming.CommunicationException: adserver.example.com:636 [Root exception
> is javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.]
> at com.sun.jndi.ldap.Connection.(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
> ...
> Caused by: javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
> ...
> Caused by: java.security.cert.CertificateException: No subject alternative
> DNS name matching adserver.example.com found.
> at
> sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
> at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
> at
> sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
> {noformat}
> Note: This occurs when the hostname embedded in the SSL certificate does not
> match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
> used. This is not seen when Oracle JDK is used.
> {noformat:title=Observed with this version of JDK}
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
> {noformat}
> {noformat:title=Not observed with this version of JDK}
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> {noformat}
> *Solution*
> The
> {{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
> class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
> nothing in the additional overridden methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
[ https://issues.apache.org/jira/browse/AMBARI-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575273#comment-16575273 ] Hudson commented on AMBARI-24367: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #126 (See [https://builds.apache.org/job/Ambari-branch-2.7/126/]) [AMBARI-24367] Fix integration test regressions in AMS collector due to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5e3d86b92fc5cc95275e384c94d98940ac973c17]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/aggregators/TimelineMetricClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/MetricTestHelper.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/discovery/TimelineMetricMetadataManager.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/StandaloneHBaseTestingUtility.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/aggregators/ITMetricAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/ITPhoenixHBaseAccessor.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/AbstractMiniHBaseClusterTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/aggregators/ITClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java > Fix integration test regressions in AMS collector due to scale changes. > --- > > Key: AMBARI-24367 > URL: https://issues.apache.org/jira/browse/AMBARI-24367 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > * Extend HBaseTestingUtility to spin up standalone HBase cluster for > integraton testing instead of distributed mode instance with HDFS. > * Fix integration test regressions from 2.7.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
[ https://issues.apache.org/jira/browse/AMBARI-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24367. Resolution: Fixed > Fix integration test regressions in AMS collector due to scale changes. > --- > > Key: AMBARI-24367 > URL: https://issues.apache.org/jira/browse/AMBARI-24367 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > * Extend HBaseTestingUtility to spin up standalone HBase cluster for > integraton testing instead of distributed mode instance with HDFS. > * Fix integration test regressions from 2.7.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
[ https://issues.apache.org/jira/browse/AMBARI-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575196#comment-16575196 ] Hudson commented on AMBARI-24367: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9778 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9778/]) AMBARI-24367 : Fix integration test regressions in AMS collector due to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=918795a3d91d001b8cd8e1ef48c5b1480beedd8b]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/aggregators/TimelineMetricClusterAggregator.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/StandaloneHBaseTestingUtility.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/AbstractMiniHBaseClusterTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/aggregators/ITMetricAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/ambari/metrics/core/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/MetricTestHelper.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/aggregators/ITClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/ambari/metrics/core/timeline/ITPhoenixHBaseAccessor.java > Fix integration test regressions in AMS collector due to scale changes. > --- > > Key: AMBARI-24367 > URL: https://issues.apache.org/jira/browse/AMBARI-24367 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h > Remaining Estimate: 0h > > * Extend HBaseTestingUtility to spin up standalone HBase cluster for > integraton testing instead of distributed mode instance with HDFS. > * Fix integration test regressions from 2.7.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24451) ambari.ldap.advanced.group_mapping_rules does not work, LDAP sync does not add admin roles for configured group(s)
Robert Levas created AMBARI-24451: - Summary: ambari.ldap.advanced.group_mapping_rules does not work, LDAP sync does not add admin roles for configured group(s) Key: AMBARI-24451 URL: https://issues.apache.org/jira/browse/AMBARI-24451 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.7.1 If I configure ambari.ldap.advanced.group_mapping_rules, it does not add ambari admin roles to the configured role. I did some debug and the AmbariLdapConfiguration is uninitialized in Users.java class, so the adminGroupMappings value is the default "Ambari Administrators" not the one I configured before. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24450) Remove dependencies with potential security vulnerabilities from fast-hdfs-resource
[
https://issues.apache.org/jira/browse/AMBARI-24450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24450:
Fix Version/s: 2.7.1
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource
> ---
>
> Key: AMBARI-24450
> URL: https://issues.apache.org/jira/browse/AMBARI-24450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource. Most issues appear to be coming from dependencies of
> org.apache.hadoop:hadoop-core:1.2.1.
> * Apache Tomcat 5.5.12 - recommendation, exclude or update to 6.0.20.0 or
> above.
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- tomcat:jasper-runtime:jar:5.5.12:compile
> [INFO]\- tomcat:jasper-compiler:jar:5.5.12:compile
> [INFO]
>
> {noformat}
> * org.mortbay.jetty:jetty:6.1.26 - exclude or update to 6.1.26-hwx
> * org.mortbay.jetty:jsp-2.1:6.1H.14.1 - exclude or update to 6.1.0.0-fuse
> * org.mortbay.jetty:servlet-api-2.5:6.1.12rc1 - exclude or update to
> 6.1.0.1-fuse
> * org.mortbay.jetty:jetty-test:6.1.26 - exclude or update to 6.1.26.hwx
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO]| \- org.mortbay.jetty:servlet-api:jar:2.5-20081211:compile
> [INFO]+- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO]+- org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:compile
> [INFO]| \- org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:compile
> [INFO]\- org.mortbay.jetty:jsp-2.1:jar:6.1.14:compile
> [INFO]
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24450) Remove dependencies with potential security vulnerabilities from fast-hdfs-resource
[
https://issues.apache.org/jira/browse/AMBARI-24450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24450:
Affects Version/s: 2.7.1
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource
> ---
>
> Key: AMBARI-24450
> URL: https://issues.apache.org/jira/browse/AMBARI-24450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource. Most issues appear to be coming from dependencies of
> org.apache.hadoop:hadoop-core:1.2.1.
> * Apache Tomcat 5.5.12 - recommendation, exclude or update to 6.0.20.0 or
> above.
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- tomcat:jasper-runtime:jar:5.5.12:compile
> [INFO]\- tomcat:jasper-compiler:jar:5.5.12:compile
> [INFO]
>
> {noformat}
> * org.mortbay.jetty:jetty:6.1.26 - exclude or update to 6.1.26-hwx
> * org.mortbay.jetty:jsp-2.1:6.1H.14.1 - exclude or update to 6.1.0.0-fuse
> * org.mortbay.jetty:servlet-api-2.5:6.1.12rc1 - exclude or update to
> 6.1.0.1-fuse
> * org.mortbay.jetty:jetty-test:6.1.26 - exclude or update to 6.1.26.hwx
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO]| \- org.mortbay.jetty:servlet-api:jar:2.5-20081211:compile
> [INFO]+- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO]+- org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:compile
> [INFO]| \- org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:compile
> [INFO]\- org.mortbay.jetty:jsp-2.1:jar:6.1.14:compile
> [INFO]
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24450) Remove dependencies with potential security vulnerabilities from fast-hdfs-resource
Dmitry Lysnichenko created AMBARI-24450:
---
Summary: Remove dependencies with potential security
vulnerabilities from fast-hdfs-resource
Key: AMBARI-24450
URL: https://issues.apache.org/jira/browse/AMBARI-24450
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Remove dependencies with potential security vulnerabilities from
fast-hdfs-resource. Most issues appear to be coming from dependencies of
org.apache.hadoop:hadoop-core:1.2.1.
* Apache Tomcat 5.5.12 - recommendation, exclude or update to 6.0.20.0 or above.
{noformat}
[INFO]
[INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ fast-hdfs-resource
---
[INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
[INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
[INFO]+- tomcat:jasper-runtime:jar:5.5.12:compile
[INFO]\- tomcat:jasper-compiler:jar:5.5.12:compile
[INFO]
{noformat}
* org.mortbay.jetty:jetty:6.1.26 - exclude or update to 6.1.26-hwx
* org.mortbay.jetty:jsp-2.1:6.1H.14.1 - exclude or update to 6.1.0.0-fuse
* org.mortbay.jetty:servlet-api-2.5:6.1.12rc1 - exclude or update to
6.1.0.1-fuse
* org.mortbay.jetty:jetty-test:6.1.26 - exclude or update to 6.1.26.hwx
{noformat}
[INFO]
[INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ fast-hdfs-resource
---
[INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
[INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
[INFO]+- org.mortbay.jetty:jetty:jar:6.1.26:compile
[INFO]| \- org.mortbay.jetty:servlet-api:jar:2.5-20081211:compile
[INFO]+- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
[INFO]+- org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:compile
[INFO]| \- org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:compile
[INFO]\- org.mortbay.jetty:jsp-2.1:jar:6.1.14:compile
[INFO]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24450) Remove dependencies with potential security vulnerabilities from fast-hdfs-resource
[
https://issues.apache.org/jira/browse/AMBARI-24450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-24450:
Component/s: ambari-server
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource
> ---
>
> Key: AMBARI-24450
> URL: https://issues.apache.org/jira/browse/AMBARI-24450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
>
> Remove dependencies with potential security vulnerabilities from
> fast-hdfs-resource. Most issues appear to be coming from dependencies of
> org.apache.hadoop:hadoop-core:1.2.1.
> * Apache Tomcat 5.5.12 - recommendation, exclude or update to 6.0.20.0 or
> above.
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- tomcat:jasper-runtime:jar:5.5.12:compile
> [INFO]\- tomcat:jasper-compiler:jar:5.5.12:compile
> [INFO]
>
> {noformat}
> * org.mortbay.jetty:jetty:6.1.26 - exclude or update to 6.1.26-hwx
> * org.mortbay.jetty:jsp-2.1:6.1H.14.1 - exclude or update to 6.1.0.0-fuse
> * org.mortbay.jetty:servlet-api-2.5:6.1.12rc1 - exclude or update to
> 6.1.0.1-fuse
> * org.mortbay.jetty:jetty-test:6.1.26 - exclude or update to 6.1.26.hwx
> {noformat}
> [INFO]
>
> [INFO] Building fast-hdfs-resource 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> fast-hdfs-resource ---
> [INFO] org.apache.ambari:fast-hdfs-resource:jar:0.0.1-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
> [INFO]+- org.mortbay.jetty:jetty:jar:6.1.26:compile
> [INFO]| \- org.mortbay.jetty:servlet-api:jar:2.5-20081211:compile
> [INFO]+- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
> [INFO]+- org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:compile
> [INFO]| \- org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:compile
> [INFO]\- org.mortbay.jetty:jsp-2.1:jar:6.1.14:compile
> [INFO]
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24447:
--
Status: Patch Available (was: Open)
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off
> --
>
> Key: AMBARI-24447
> URL: https://issues.apache.org/jira/browse/AMBARI-24447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off.
> {noformat}
> 2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
> ADKerberosOperationHandler:471 - Failed to communicate with the Active
> Directory at ldaps://adserver.example.com:636: adserver.example.com:636
> javax.naming.CommunicationException: adserver.example.com:636 [Root exception
> is javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.]
> at com.sun.jndi.ldap.Connection.(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
> ...
> Caused by: javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
> ...
> Caused by: java.security.cert.CertificateException: No subject alternative
> DNS name matching adserver.example.com found.
> at
> sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
> at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
> at
> sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
> {noformat}
> Note: This occurs when the hostname embedded in the SSL certificate does not
> match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
> used. This is not seen when Oracle JDK is used.
> {noformat:title=Observed with this version of JDK}
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
> {noformat}
> {noformat:title=Not observed with this version of JDK}
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> {noformat}
> *Solution*
> The
> {{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
> class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
> nothing in the additional overridden methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24447:
Labels: pull-request-available (was: )
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off
> --
>
> Key: AMBARI-24447
> URL: https://issues.apache.org/jira/browse/AMBARI-24447
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> No subject alternative DNS name exception encountered when Enabling Kerberos
> against an Active Directory even when SSL verification is off.
> {noformat}
> 2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
> ADKerberosOperationHandler:471 - Failed to communicate with the Active
> Directory at ldaps://adserver.example.com:636: adserver.example.com:636
> javax.naming.CommunicationException: adserver.example.com:636 [Root exception
> is javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.]
> at com.sun.jndi.ldap.Connection.(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
> ...
> Caused by: javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateException: No subject alternative DNS name
> matching adserver.example.com found.
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
> ...
> Caused by: java.security.cert.CertificateException: No subject alternative
> DNS name matching adserver.example.com found.
> at
> sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
> at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
> at
> sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
> at
> sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
> {noformat}
> Note: This occurs when the hostname embedded in the SSL certificate does not
> match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
> used. This is not seen when Oracle JDK is used.
> {noformat:title=Observed with this version of JDK}
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
> {noformat}
> {noformat:title=Not observed with this version of JDK}
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> {noformat}
> *Solution*
> The
> {{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
> class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
> nothing in the additional overridden methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24448) "Druid Historical" default MaxDirectMemorySize=1TB
[
https://issues.apache.org/jira/browse/AMBARI-24448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24448:
--
Labels: common-services druid (was: )
> "Druid Historical" default MaxDirectMemorySize=1TB
> --
>
> Key: AMBARI-24448
> URL: https://issues.apache.org/jira/browse/AMBARI-24448
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.2, 2.7.0
>Reporter: Sean Roberts
>Priority: Major
> Labels: common-services, druid
>
> By default, Ambari is giving "Druid Historical" component
> -XX:MaxDirectMemorySize=1048576m
> I'm asking the Druid devs what a good default is, but 1TB of RAM is
> definitely too much! Once I get an answer, can send a pull request over.
> `-XX:MaxDirectMemorySize` comes from druid-env.
> druid.historical.jvm.direct.memory and is appended with ‘m’:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/druid.py#L109-L114
> The default value is ‘1048576` which, when appeneded with 'm', is 1TB!:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/DRUID/0.10.1/configuration/druid-env.xml#L130-L131
> Process listing:
> {code}
> $ ps aux | grep ^druid.*historical
> druid 115683 0.0 15.6 97802020 82774676 ? Sl Jun08 66:48
> /usr/java/default/bin/java -server -Xms2048m -Xmx2048m
> -XX:MaxDirectMemorySize=1048576m
> {code}
> In the JVM config file which Ambari manages:
> {code}
> $ grep MaxDirect /usr/hdp/current/druid-historical/conf/historical/jvm.config
> -XX:MaxDirectMemorySize=1048576m
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24415) Remove dependencies with CVE issues from Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575136#comment-16575136
]
Hudson commented on AMBARI-24415:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #125 (See
[https://builds.apache.org/job/Ambari-branch-2.7/125/])
[AMBARI-24415] Remove dependencies with CVE issues from Ambari Server (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3a691ddb39f6fae45921cb20a7af65879aa7462b])
* (edit) ambari-server/pom.xml
* (edit) ambari-project/pom.xml
> Remove dependencies with CVE issues from Ambari Server
> --
>
> Key: AMBARI-24415
> URL: https://issues.apache.org/jira/browse/AMBARI-24415
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: cleanup, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Remove dependencies with CVE issues from Ambari Server
> * org.springframework:spring-beans:jar before 4.3.17.RELEASE
> ** CVE-2018-1270 - https://nvd.nist.gov/vuln/detail/CVE-2018-1270
> ** CVE-2018-1275 - https://nvd.nist.gov/vuln/detail/CVE-2018-1275
> ** CVE-2018-1199 - https://nvd.nist.gov/vuln/detail/CVE-2018-1199
> ** CVE-2018-1271 - https://nvd.nist.gov/vuln/detail/CVE-2018-1271
> ** CVE-2018-1257 - https://nvd.nist.gov/vuln/detail/CVE-2018-1257
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \-
> org.springframework.security:spring-security-core:jar:4.2.4.RELEASE:compile
> [INFO]\- org.springframework:spring-beans:jar:4.3.12.RELEASE:compile
> {noformat}
> * org.kohsuke:libpam4j:jar before version 1.9
> ** CVE-2017-12197 - https://nvd.nist.gov/vuln/detail/CVE-2017-12197
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- org.kohsuke:libpam4j:jar:1.8:compile
> {noformat}
> * org.springframework:spring-context before version 4.3.17.RELEASE
> ** CVE-2018-1257 - https://nvd.nist.gov/vuln/detail/CVE-2018-1257
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- org.springframework:spring-context:jar:4.3.16.RELEASE:compile
> {noformat}
> * org.springframework.security:spring-security-ldap:jar before version
> 4.1.5.RELEASE
> ** CVE-2018-1199 - https://nvd.nist.gov/vuln/detail/CVE-2018-1199
> ** CVE-2016-9879 - https://nvd.nist.gov/vuln/detail/CVE-2016-9879
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \-
> org.springframework.security:spring-security-ldap:jar:4.1.1.RELEASE:compile
> {noformat}
> * com.jcraft:jsch:jar before version 1.54
> ** CVE-2016-5725 - https://nvd.nist.gov/vuln/detail/CVE-2016-5725
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- com.jcraft:jsch:jar:0.1.45:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
[
https://issues.apache.org/jira/browse/AMBARI-24447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24447:
--
Description:
No subject alternative DNS name exception encountered when Enabling Kerberos
against an Active Directory even when SSL verification is off.
{noformat}
2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
ADKerberosOperationHandler:471 - Failed to communicate with the Active
Directory at ldaps://adserver.example.com:636: adserver.example.com:636
javax.naming.CommunicationException: adserver.example.com:636 [Root exception
is javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.]
at com.sun.jndi.ldap.Connection.(Connection.java:238)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
...
Caused by: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
...
Caused by: java.security.cert.CertificateException: No subject alternative DNS
name matching adserver.example.com found.
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
at
sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
{noformat}
Note: This occurs when the hostname embedded in the SSL certificate does not
match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
used. This is not seen when Oracle JDK is used.
{noformat:title=Observed with this version of JDK}
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
{noformat}
{noformat:title=Not observed with this version of JDK}
java version "1.8.0_112"
Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
{noformat}
*Solution*
The
{{org.apache.ambari.server.security.InternalSSLSocketFactory.LenientTrustManager}}
class needs to extend {{javax.net.ssl.X509ExtendedTrustManager}} and do
nothing in the additional overridden methods.
was:
No subject alternative DNS name exception encountered when Enabling Kerberos
against an Active Directory even when SSL verification is off.
{noformat}
2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
ADKerberosOperationHandler:471 - Failed to communicate with the Active
Directory at ldaps://adserver.example.com:636: adserver.example.com:636
javax.naming.CommunicationException: adserver.example.com:636 [Root exception
is javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.]
at com.sun.jndi.ldap.Connection.(Connection.java:238)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
...
Caused by: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
...
Caused by: java.security.cert.CertificateException: No subject alternative DNS
name matching adserver.example.com found.
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
at
sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
{noformat}
Note: This occurs when the hostname embedded in the SSL certificate does not
match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
used. This is not seen when Oracle JDK is used.
{noformat:title=Observed with this version of JDK}
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
{noformat}
{noformat:title=Not observed with this version of JDK}
java version "1.8.0_112"
Java(TM) SE Runtime Environment (build
[jira] [Created] (AMBARI-24449) Allow For Pluggable Stack Tests
Jonathan Hurley created AMBARI-24449:
Summary: Allow For Pluggable Stack Tests
Key: AMBARI-24449
URL: https://issues.apache.org/jira/browse/AMBARI-24449
Project: Ambari
Issue Type: Task
Affects Versions: 3.0.0
Reporter: Jonathan Hurley
Fix For: 3.0.0
AMBARI-24446 removed all of the stacks which were checked into Apache's
codebase. This included the HDP stack. As of Ambari 3.0, no stacks will ship
with Ambari, which means that all of the stacks (and the stack test code) has
to be removed.
For users of Ambari which will be providing their own stacks, such as HDP 3.0,
they will need a way to consume the Ambari Python libraries and run their own
tests against their stack.
- {{RMFTestCase}} must be refactored to allow for invokers to specify paths to
their custom stacks
- The test framework and common python library must be exposed in a consumable
package for testing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24448) "Druid Historical" default MaxDirectMemorySize=1TB
Sean Roberts created AMBARI-24448:
-
Summary: "Druid Historical" default MaxDirectMemorySize=1TB
Key: AMBARI-24448
URL: https://issues.apache.org/jira/browse/AMBARI-24448
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.6.2, 2.7.0
Reporter: Sean Roberts
By default, Ambari is giving "Druid Historical" component
-XX:MaxDirectMemorySize=1048576m
I'm asking the Druid devs what a good default is, but 1TB of RAM is definitely
too much! Once I get an answer, can send a pull request over.
`-XX:MaxDirectMemorySize` comes from druid-env.
druid.historical.jvm.direct.memory and is appended with ‘m’:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/druid.py#L109-L114
The default value is ‘1048576` which, when appeneded with 'm', is 1TB!:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/DRUID/0.10.1/configuration/druid-env.xml#L130-L131
Process listing:
{code}
$ ps aux | grep ^druid.*historical
druid 115683 0.0 15.6 97802020 82774676 ? Sl Jun08 66:48
/usr/java/default/bin/java -server -Xms2048m -Xmx2048m
-XX:MaxDirectMemorySize=1048576m
{code}
In the JVM config file which Ambari manages:
{code}
$ grep MaxDirect /usr/hdp/current/druid-historical/conf/historical/jvm.config
-XX:MaxDirectMemorySize=1048576m
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24447) No subject alternative DNS name exception encountered when Enabling Kerberos against an Active Directory even when SSL verification is off
Robert Levas created AMBARI-24447:
-
Summary: No subject alternative DNS name exception encountered
when Enabling Kerberos against an Active Directory even when SSL verification
is off
Key: AMBARI-24447
URL: https://issues.apache.org/jira/browse/AMBARI-24447
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.1
No subject alternative DNS name exception encountered when Enabling Kerberos
against an Active Directory even when SSL verification is off.
{noformat}
2018-08-09 14:48:28,275 WARN [ambari-client-thread-35]
ADKerberosOperationHandler:471 - Failed to communicate with the Active
Directory at ldaps://adserver.example.com:636: adserver.example.com:636
javax.naming.CommunicationException: adserver.example.com:636 [Root exception
is javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.]
at com.sun.jndi.ldap.Connection.(Connection.java:238)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)
...
Caused by: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No subject alternative DNS name
matching adserver.example.com found.
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
...
Caused by: java.security.cert.CertificateException: No subject alternative DNS
name matching adserver.example.com found.
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
at
sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:459)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1026)
at
sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:993)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
{noformat}
Note: This occurs when the hostname embedded in the SSL certificate does not
match the hostname of the Active Directory host and Open JDK 1.8.181-b13 is
used. This is not seen when Oracle JDK is used.
{noformat:title=Observed with this version of JDK}
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
{noformat}
{noformat:title=Not observed with this version of JDK}
java version "1.8.0_112"
Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24446) Removal of Unsupported Stacks
[ https://issues.apache.org/jira/browse/AMBARI-24446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24446: Labels: pull-request-available (was: ) > Removal of Unsupported Stacks > - > > Key: AMBARI-24446 > URL: https://issues.apache.org/jira/browse/AMBARI-24446 > Project: Ambari > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > > Ambari 3.0 will no longer support the stacks which currently exist in the > Apache repository. The following stacks should be removed: > - BIGTOP > - HDP > - HDPWIN > - PERF > - PHD > With Ambari 3.0, all stacks will be delivered via management packs. This > furthers the goal of making Ambari a framework where providers can plugin > their own stack-based logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24446) Removal of Unsupported Stacks
Jonathan Hurley created AMBARI-24446: Summary: Removal of Unsupported Stacks Key: AMBARI-24446 URL: https://issues.apache.org/jira/browse/AMBARI-24446 Project: Ambari Issue Type: Task Affects Versions: 3.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 3.0.0 Ambari 3.0 will no longer support the stacks which currently exist in the Apache repository. The following stacks should be removed: - BIGTOP - HDP - HDPWIN - PERF - PHD With Ambari 3.0, all stacks will be delivered via management packs. This furthers the goal of making Ambari a framework where providers can plugin their own stack-based logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24415) Remove dependencies with CVE issues from Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24415:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove dependencies with CVE issues from Ambari Server
> --
>
> Key: AMBARI-24415
> URL: https://issues.apache.org/jira/browse/AMBARI-24415
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: cleanup, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Remove dependencies with CVE issues from Ambari Server
> * org.springframework:spring-beans:jar before 4.3.17.RELEASE
> ** CVE-2018-1270 - https://nvd.nist.gov/vuln/detail/CVE-2018-1270
> ** CVE-2018-1275 - https://nvd.nist.gov/vuln/detail/CVE-2018-1275
> ** CVE-2018-1199 - https://nvd.nist.gov/vuln/detail/CVE-2018-1199
> ** CVE-2018-1271 - https://nvd.nist.gov/vuln/detail/CVE-2018-1271
> ** CVE-2018-1257 - https://nvd.nist.gov/vuln/detail/CVE-2018-1257
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \-
> org.springframework.security:spring-security-core:jar:4.2.4.RELEASE:compile
> [INFO]\- org.springframework:spring-beans:jar:4.3.12.RELEASE:compile
> {noformat}
> * org.kohsuke:libpam4j:jar before version 1.9
> ** CVE-2017-12197 - https://nvd.nist.gov/vuln/detail/CVE-2017-12197
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- org.kohsuke:libpam4j:jar:1.8:compile
> {noformat}
> * org.springframework:spring-context before version 4.3.17.RELEASE
> ** CVE-2018-1257 - https://nvd.nist.gov/vuln/detail/CVE-2018-1257
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- org.springframework:spring-context:jar:4.3.16.RELEASE:compile
> {noformat}
> * org.springframework.security:spring-security-ldap:jar before version
> 4.1.5.RELEASE
> ** CVE-2018-1199 - https://nvd.nist.gov/vuln/detail/CVE-2018-1199
> ** CVE-2016-9879 - https://nvd.nist.gov/vuln/detail/CVE-2016-9879
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \-
> org.springframework.security:spring-security-ldap:jar:4.1.1.RELEASE:compile
> {noformat}
> * com.jcraft:jsch:jar before version 1.54
> ** CVE-2016-5725 - https://nvd.nist.gov/vuln/detail/CVE-2016-5725
> {noformat}
> [INFO] org.apache.ambari:ambari-server:jar:2.7.0.0.0
> [INFO] \- com.jcraft:jsch:jar:0.1.45:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
[ https://issues.apache.org/jira/browse/AMBARI-24442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16575051#comment-16575051 ] Hudson commented on AMBARI-24442: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9777 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9777/]) AMBARI-24442. HIVESERVER2 JDBC URL doesn't fit inside block (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1b20bcd902f57041b2a20925a713817737ef7547]) * (edit) ambari-web/app/styles/application.less > HIVESERVER2 JDBC URL doesn't fit inside block > -- > > Key: AMBARI-24442 > URL: https://issues.apache.org/jira/browse/AMBARI-24442 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > On Hive Service Summary page text doesn't fit inside the appropriate block if > HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24429) Remove dependencies with CVE issues from Ambari Agent
[
https://issues.apache.org/jira/browse/AMBARI-24429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574978#comment-16574978
]
Hudson commented on AMBARI-24429:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9776 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9776/])
[AMBARI-24429] Remove dependencies with CVE issues from Ambari Agent (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c9965c0667f1c8a8f03ff209d6b91a065d32bf9a])
* (edit) contrib/views/utils/pom.xml
> Remove dependencies with CVE issues from Ambari Agent
> -
>
> Key: AMBARI-24429
> URL: https://issues.apache.org/jira/browse/AMBARI-24429
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: cleanup, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependencies with CVE issues from Ambari Agent
> * org.apache.commons:commons-collections4:jar before version 4.0-alpha1-RC1
> ** CVE-2015-6420 - https://nvd.nist.gov/vuln/detail/CVE-2015-6420
> {noformat}
> [INFO] org.apache.ambari.contrib.views:ambari-views-utils:jar:2.0.0.0-SNAPSHOT
> [INFO] \- org.apache.commons:commons-collections4:jar:4.0:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24432) Cover federation wizardcontroller with tests
[ https://issues.apache.org/jira/browse/AMBARI-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574977#comment-16574977 ] Hudson commented on AMBARI-24432: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9776 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9776/]) AMBARI-24432. Cover federation wizardcontroller with tests (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1ca963c14c4a70f221e5cd5b4675bca6e82d4bb4]) * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/controllers/main/admin/federation/wizard_controller_test.js > Cover federation wizardcontroller with tests > > > Key: AMBARI-24432 > URL: https://issues.apache.org/jira/browse/AMBARI-24432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
[ https://issues.apache.org/jira/browse/AMBARI-24442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24442. -- Resolution: Fixed > HIVESERVER2 JDBC URL doesn't fit inside block > -- > > Key: AMBARI-24442 > URL: https://issues.apache.org/jira/browse/AMBARI-24442 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > On Hive Service Summary page text doesn't fit inside the appropriate block if > HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24429) Remove dependencies with CVE issues from Ambari Agent
[
https://issues.apache.org/jira/browse/AMBARI-24429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574938#comment-16574938
]
Hudson commented on AMBARI-24429:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #124 (See
[https://builds.apache.org/job/Ambari-branch-2.7/124/])
[AMBARI-24429] Remove dependencies with CVE issues from Ambari Agent (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cb1794e998d79aa755e4ac7e27cd0f0cf57ffb0e])
* (edit) contrib/views/utils/pom.xml
> Remove dependencies with CVE issues from Ambari Agent
> -
>
> Key: AMBARI-24429
> URL: https://issues.apache.org/jira/browse/AMBARI-24429
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: cleanup, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependencies with CVE issues from Ambari Agent
> * org.apache.commons:commons-collections4:jar before version 4.0-alpha1-RC1
> ** CVE-2015-6420 - https://nvd.nist.gov/vuln/detail/CVE-2015-6420
> {noformat}
> [INFO] org.apache.ambari.contrib.views:ambari-views-utils:jar:2.0.0.0-SNAPSHOT
> [INFO] \- org.apache.commons:commons-collections4:jar:4.0:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24348) Update description of Save Admin Credentials
[ https://issues.apache.org/jira/browse/AMBARI-24348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24348. -- Resolution: Fixed > Update description of Save Admin Credentials > > > Key: AMBARI-24348 > URL: https://issues.apache.org/jira/browse/AMBARI-24348 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Change tooltip description to 'Ambari must be configured to encrypt the > passwords stored in Ambari before you can save admin credentials' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23244) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-23244. -- Resolution: Fixed > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23244 > URL: https://issues.apache.org/jira/browse/AMBARI-23244 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-23298. -- Resolution: Fixed > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23298 > URL: https://issues.apache.org/jira/browse/AMBARI-23298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24246) Ambari does not pick the existing hive database from the jdbc url set
[ https://issues.apache.org/jira/browse/AMBARI-24246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24246: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari does not pick the existing hive database from the jdbc url set > - > > Key: AMBARI-24246 > URL: https://issues.apache.org/jira/browse/AMBARI-24246 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24432) Cover federation wizardcontroller with tests
[ https://issues.apache.org/jira/browse/AMBARI-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24432. -- Resolution: Fixed > Cover federation wizardcontroller with tests > > > Key: AMBARI-24432 > URL: https://issues.apache.org/jira/browse/AMBARI-24432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24432) Cover federation wizardcontroller with tests
[ https://issues.apache.org/jira/browse/AMBARI-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574912#comment-16574912 ] Antonenko Alexander commented on AMBARI-24432: -- Committed to trunk > Cover federation wizardcontroller with tests > > > Key: AMBARI-24432 > URL: https://issues.apache.org/jira/browse/AMBARI-24432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24445) [Log Search UI] exclude mock data from production build
[ https://issues.apache.org/jira/browse/AMBARI-24445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24445: Labels: pull-request-available (was: ) > [Log Search UI] exclude mock data from production build > --- > > Key: AMBARI-24445 > URL: https://issues.apache.org/jira/browse/AMBARI-24445 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > > Currently, mock data is included to production build code, which is redundant. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24429) Remove dependencies with CVE issues from Ambari Agent
[
https://issues.apache.org/jira/browse/AMBARI-24429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24429:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove dependencies with CVE issues from Ambari Agent
> -
>
> Key: AMBARI-24429
> URL: https://issues.apache.org/jira/browse/AMBARI-24429
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: cleanup, pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependencies with CVE issues from Ambari Agent
> * org.apache.commons:commons-collections4:jar before version 4.0-alpha1-RC1
> ** CVE-2015-6420 - https://nvd.nist.gov/vuln/detail/CVE-2015-6420
> {noformat}
> [INFO] org.apache.ambari.contrib.views:ambari-views-utils:jar:2.0.0.0-SNAPSHOT
> [INFO] \- org.apache.commons:commons-collections4:jar:4.0:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24445) [Log Search UI] exclude mock data from production build
Istvan Tobias created AMBARI-24445: -- Summary: [Log Search UI] exclude mock data from production build Key: AMBARI-24445 URL: https://issues.apache.org/jira/browse/AMBARI-24445 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Currently, mock data is included to production build code, which is redundant. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574830#comment-16574830 ] Hudson commented on AMBARI-24443: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9772 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9772/]) AMBARI-24443. Slider type widget displays erroneously before first touch (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=514db78c27a70c2883392b9c26728fd3eb341b06]) * (edit) ambari-web/app/views/common/configs/widgets/slider_config_widget_view.js > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24444) Tooltip For Zeppelin "zeppelin.ssl.keystore.path" wrong
Attila Csaba Marosi created AMBARI-2: Summary: Tooltip For Zeppelin "zeppelin.ssl.keystore.path" wrong Key: AMBARI-2 URL: https://issues.apache.org/jira/browse/AMBARI-2 Project: Ambari Issue Type: Bug Affects Versions: trunk, 2.7.0 Reporter: Attila Csaba Marosi The tooltip for zeppelin.ssl.keystore.path displays "Path to keystore relative to Zeppelin home", but based on Zeppelin documentation [1] it is relative to the configuration directory: "Path to keystore relative to Zeppelin configuration directory". Proposed diff: diff --git a/ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-config.xml b/ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-config.xml index dfecae6f52..06c3952b7c 100644 --- a/ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-config.xml +++ b/ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-config.xml @@ -127,7 +127,7 @@ zeppelin.ssl.keystore.path conf/keystore -Path to keystore relative to Zeppelin home +Path to keystore relative to Zeppelin configuration directory [1] https://zeppelin.apache.org/docs/0.7.0/install/configuration.html#configuring-server-side-ssl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24443. -- Resolution: Fixed > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
[ https://issues.apache.org/jira/browse/AMBARI-24442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24442: Labels: pull-request-available (was: ) > HIVESERVER2 JDBC URL doesn't fit inside block > -- > > Key: AMBARI-24442 > URL: https://issues.apache.org/jira/browse/AMBARI-24442 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > On Hive Service Summary page text doesn't fit inside the appropriate block if > HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24443: Labels: pull-request-available (was: ) > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. See attached video. > STR as seen on the attached video: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. STR: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs in the cluster http://104.196.74.255:8080/ 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point whet the slider is. See attached video. > STR as seen on the attached video: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24443) Slider type widget displays erroneously before first touch
Aleksandr Kovalenko created AMBARI-24443: Summary: Slider type widget displays erroneously before first touch Key: AMBARI-24443 URL: https://issues.apache.org/jira/browse/AMBARI-24443 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs in the cluster http://104.196.74.255:8080/ 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
Aleksandr Kovalenko created AMBARI-24442: Summary: HIVESERVER2 JDBC URL doesn't fit inside block Key: AMBARI-24442 URL: https://issues.apache.org/jira/browse/AMBARI-24442 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 On Hive Service Summary page text doesn't fit inside the appropriate block if HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24441) [Log Search UI] The graphs are not always resized on window resize event.
Istvan Tobias created AMBARI-24441: -- Summary: [Log Search UI] The graphs are not always resized on window resize event. Key: AMBARI-24441 URL: https://issues.apache.org/jira/browse/AMBARI-24441 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias When the user resizes the browser window the graphs/charts are do not resized fully. Expectation: every time when the browser window resized the graph width should be recalculated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24434) Cannot deploy HBase without HDFS
[ https://issues.apache.org/jira/browse/AMBARI-24434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24434: Labels: pull-request-available (was: ) > Cannot deploy HBase without HDFS > > > Key: AMBARI-24434 > URL: https://issues.apache.org/jira/browse/AMBARI-24434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > > HBase can store data on filesystems other than HDFS, but Ambari cannot deploy > it without HDFS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24440) [Log Search UI] Default logs list length per page should be 100 instead of 10
Istvan Tobias created AMBARI-24440: -- Summary: [Log Search UI] Default logs list length per page should be 100 instead of 10 Key: AMBARI-24440 URL: https://issues.apache.org/jira/browse/AMBARI-24440 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Default logs list length per page should be 100 instead of 10 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24439) [Log Search UI] center the log tabs so they're aligned with the buttons
Istvan Tobias created AMBARI-24439: -- Summary: [Log Search UI] center the log tabs so they're aligned with the buttons Key: AMBARI-24439 URL: https://issues.apache.org/jira/browse/AMBARI-24439 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Center the log screen tabs so they're aligned with the buttons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24438) [Log Search UI] App Loader Page - add initial progress state
[ https://issues.apache.org/jira/browse/AMBARI-24438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24438: --- Description: Add some initial progress state to the app loader progress bar: * initial x% value * indeterminate progress bar was: Add some initial progress state to the app loader progressbar: * initial x% value * indeterminate progress bar > [Log Search UI] App Loader Page - add initial progress state > > > Key: AMBARI-24438 > URL: https://issues.apache.org/jira/browse/AMBARI-24438 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Add some initial progress state to the app loader progress bar: > * initial x% value > * indeterminate progress bar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24438) [Log Search UI] App Loader Page - add initial progress state
Istvan Tobias created AMBARI-24438: -- Summary: [Log Search UI] App Loader Page - add initial progress state Key: AMBARI-24438 URL: https://issues.apache.org/jira/browse/AMBARI-24438 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Add some initial progress state to the app loader progressbar: * initial x% value * indeterminate progress bar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24432) Cover federation wizardcontroller with tests
[ https://issues.apache.org/jira/browse/AMBARI-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24432: Labels: pull-request-available (was: ) > Cover federation wizardcontroller with tests > > > Key: AMBARI-24432 > URL: https://issues.apache.org/jira/browse/AMBARI-24432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24437) [Log Search UI] App Loader Page - add more space above the loader animations
Istvan Tobias created AMBARI-24437: -- Summary: [Log Search UI] App Loader Page - add more space above the loader animations Key: AMBARI-24437 URL: https://issues.apache.org/jira/browse/AMBARI-24437 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Add space above the loader animations to be more separated from the top. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24436) [Log Search UI] App Loader Page - Align the logo left
Istvan Tobias created AMBARI-24436: -- Summary: [Log Search UI] App Loader Page - Align the logo left Key: AMBARI-24436 URL: https://issues.apache.org/jira/browse/AMBARI-24436 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Align left the logo on the application loader page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
Istvan Tobias created AMBARI-24435: -- Summary: [Log Search UI] Remove underline text decoration from dropdowns on hover Key: AMBARI-24435 URL: https://issues.apache.org/jira/browse/AMBARI-24435 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias The dropdown buttons have underline text decoration on mouse hover, it should be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24434) Cannot deploy HBase without HDFS
Doroszlai, Attila created AMBARI-24434: -- Summary: Cannot deploy HBase without HDFS Key: AMBARI-24434 URL: https://issues.apache.org/jira/browse/AMBARI-24434 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Fix For: 2.7.1 HBase can store data on filesystems other than HDFS, but Ambari cannot deploy it without HDFS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24431) Infra Manager / Log Search: Fix Jetty CVE-2018-12536
[ https://issues.apache.org/jira/browse/AMBARI-24431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24431. --- Resolution: Fixed > Infra Manager / Log Search: Fix Jetty CVE-2018-12536 > - > > Key: AMBARI-24431 > URL: https://issues.apache.org/jira/browse/AMBARI-24431 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24422) Log Feeder: upgrade guava version (because of CVE-2018-10237)
[ https://issues.apache.org/jira/browse/AMBARI-24422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24422. --- Resolution: Fixed > Log Feeder: upgrade guava version (because of CVE-2018-10237) > - > > Key: AMBARI-24422 > URL: https://issues.apache.org/jira/browse/AMBARI-24422 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24433) [Log Search UI] Reset to default selection in the dropdowns
[ https://issues.apache.org/jira/browse/AMBARI-24433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24433: --- Description: Table list column selection: create an action button to reset the selection to the default. (was: Table list column selection: create a action button to reset the selection to the default.) > [Log Search UI] Reset to default selection in the dropdowns > --- > > Key: AMBARI-24433 > URL: https://issues.apache.org/jira/browse/AMBARI-24433 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Original Estimate: 6h > Remaining Estimate: 6h > > Table list column selection: create an action button to reset the selection > to the default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24433) [Log Search UI] Reset to default selection in the dropdowns
Istvan Tobias created AMBARI-24433: -- Summary: [Log Search UI] Reset to default selection in the dropdowns Key: AMBARI-24433 URL: https://issues.apache.org/jira/browse/AMBARI-24433 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Table list column selection: create a action button to reset the selection to the default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24412) Unit tests for federation step 4 controller
[ https://issues.apache.org/jira/browse/AMBARI-24412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574461#comment-16574461 ] Hudson commented on AMBARI-24412: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9771 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9771/]) AMBARI-24412. Unit tests for federation step 4 controller (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=853ac1441573715ab955f51b0dace3f569200d34]) * (edit) ambari-web/app/assets/test/tests.js * (add) ambari-web/test/controllers/main/admin/federation/step4_controller_test.js > Unit tests for federation step 4 controller > --- > > Key: AMBARI-24412 > URL: https://issues.apache.org/jira/browse/AMBARI-24412 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24432) Cover federation wizardcontroller with tests
[ https://issues.apache.org/jira/browse/AMBARI-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24432: Assignee: Antonenko Alexander > Cover federation wizardcontroller with tests > > > Key: AMBARI-24432 > URL: https://issues.apache.org/jira/browse/AMBARI-24432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24432) Cover federation wizardcontroller with tests
Antonenko Alexander created AMBARI-24432: Summary: Cover federation wizardcontroller with tests Key: AMBARI-24432 URL: https://issues.apache.org/jira/browse/AMBARI-24432 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24412) Unit tests for federation step 4 controller
[ https://issues.apache.org/jira/browse/AMBARI-24412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24412. -- Resolution: Fixed Committed to trunk > Unit tests for federation step 4 controller > --- > > Key: AMBARI-24412 > URL: https://issues.apache.org/jira/browse/AMBARI-24412 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
