python2.7.18 call connect_get_namespaced_pod_exec get Hostname doesn't match but call list_namespaced_pod is normal

[hdlife007]

python 2.7.18
kubernetes 12.0.1

I have been attempted https://github.com/kubernetes-client/python/blob/master/requirements.txt and https://github.com/kubernetes-client/python/blob/master/examples/pod_exec.py, but I still got error like:
File "E:\Python27\lib\site-packages\kubernetes\stream\stream.py", line 35, in _websocket_reqeust
return api_method(*args, **kwargs)
File "E:\Python27\lib\site-packages\kubernetes\client\api\core_v1_api.py", line 994, in connect_get_namespaced_pod_exec
return self.connect_get_namespaced_pod_exec_with_http_info(name, namespace, **kwargs) # noqa: E501
File "E:\Python27\lib\site-packages\kubernetes\client\api\core_v1_api.py", line 1115, in connect_get_namespaced_pod_exec_with_http_info
collection_formats=collection_formats)
File "E:\Python27\lib\site-packages\kubernetes\client\api_client.py", line 353, in call_api
_preload_content, _request_timeout, _host)
File "E:\Python27\lib\site-packages\kubernetes\client\api_client.py", line 184, in __call_api
_request_timeout=_request_timeout)
File "E:\Python27\lib\site-packages\kubernetes\stream\ws_client.py", line 474, in websocket_call
raise ApiException(status=0, reason=str(e))
ApiException: (0)
Reason: hostname '' doesn't match either of '

[roycaihw]

/assign @yliaog

[yliaog]

#409 (comment)

please see if upgrading openssl helps.

[hdlife007]

It's no use upgrading OpenSSL
my version now is
OpenSSL 1.1.1k 25 Mar 2021

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.