[
https://issues.apache.org/jira/browse/AMBARI-23449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427362#comment-16427362
]
Endre Major commented on AMBARI-23449:
--------------------------------------
This is the root cause:
{code}
Traceback (most recent call last):
File
"/Users/emajor/w/ambari/ambari/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/Users/emajor/w/ambari/ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_metrics_deviation.py",
line 135, in test_alert_vip
self.make_alert_tests(configs, conn_mock)
File
"/Users/emajor/w/ambari/ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_metrics_deviation.py",
line 235, in make_alert_tests
[status, messages] = alert.execute(configurations=configs,
parameters=parameters, host_name=_host_name)
File
"/Users/emajor/w/ambari/ambari/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
line 328, in execute
_ssl_version =
AmbariConfig.get_resolved_config().get_force_https_protocol_value()
File
"/Users/emajor/w/ambari/ambari/ambari-agent/src/main/python/ambari_agent/AmbariConfig.py",
line 333, in get_force_https_protocol_value
return getattr(ssl, self.get_force_https_protocol_name())
AttributeError: 'module' object has no attribute 'PROTOCOL_TLSv1_2'
{code}
I hope it helps.
> Agent can not to connect to server during blueprint deploy
> ----------------------------------------------------------
>
> Key: AMBARI-23449
> URL: https://issues.apache.org/jira/browse/AMBARI-23449
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
> Affects Versions: 2.7.0
> Environment: Suse 12 sp3
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Blueprint deploy was hunged on hosts assignments.
> ambari-agent.log:
> INFO 2018-03-27 15:23:58,132 NetUtil.py:61 - Connecting to
> https://ctr-e138-1518143905142-164693-01-000002.hwx.site:8440/connection_info
> INFO 2018-03-27 15:23:58,155 security.py:59 - Server require two-way SSL
> authentication. Use it instead of one-way...
> INFO 2018-03-27 15:23:58,155 security.py:61 - Connecting to
> wss://ctr-e138-1518143905142-164693-01-000002.hwx.site:8441/agent/stomp/v1
> INFO 2018-03-27 15:23:58,155 security.py:207 - Server certicate exists, ok
> INFO 2018-03-27 15:23:58,155 security.py:215 - Agent key exists, ok
> INFO 2018-03-27 15:23:58,156 security.py:223 - Agent certificate exists, ok
> WARNING 2018-03-27 15:23:58,161 security.py:99 - Could not connect to
> wss://ctr-e138-1518143905142-164693-01-000002.hwx.site:8441/agent/stomp/v1.
> [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure
> (_ssl.c:661)
> INFO 2018-03-27 15:23:58,161 HeartbeatThread.py:99 - Connection error "[SSL:
> SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:661)".
> Re-running the registration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
