Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On macOS odo on crc return "net/http: TLS handshake timeout" #3850

Closed
lubomben opened this issue Aug 27, 2020 · 8 comments
Closed

On macOS odo on crc return "net/http: TLS handshake timeout" #3850

lubomben opened this issue Aug 27, 2020 · 8 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lubomben
Copy link

/kind bug

What versions of software are you using?

Operating System: macOS Catalina (10.15.6)

Output of odo version: odo v1.2.5 (0aeec48)

How did you run odo exactly?

After started crc (1.15) oc login is ok but "odo login" return the following error:

~/Utils/OpenShift/crc/crc-macos-1.15.0-amd64 % odo login -u developer -p developer
Connecting to the OpenShift cluster

 ✗  net/http: TLS handshake timeout

Actual behavior

net/http: TLS handshake timeout

Expected behavior

Login to the OCP cluster

Any logs, error output, etc?

~/Utils/OpenShift/crc/crc-macos-1.15.0-amd64 % odo login -u developer -p developer https://api.crc.testing:6443 -v 9
I0827 14:05:18.544377   29736 loader.go:375] Config loaded from file:  /Users/luca/.kube/config
Connecting to the OpenShift cluster

I0827 14:05:18.548108   29736 round_trippers.go:423] curl -k -v -XHEAD  'https://api.crc.testing:6443/'
I0827 14:05:18.579700   29736 round_trippers.go:443] HEAD https://api.crc.testing:6443/ 403 Forbidden in 31 milliseconds
I0827 14:05:18.579731   29736 round_trippers.go:449] Response Headers:
I0827 14:05:18.579740   29736 round_trippers.go:452]     X-Kubernetes-Pf-Flowschema-Uid: 945be23f-796b-4020-8674-1e9a3d39f5e6
I0827 14:05:18.579746   29736 round_trippers.go:452]     X-Kubernetes-Pf-Prioritylevel-Uid: 3ce58648-2ee5-4df0-a945-035c4f7fe1c7
I0827 14:05:18.579752   29736 round_trippers.go:452]     Content-Length: 186
I0827 14:05:18.579757   29736 round_trippers.go:452]     Date: Thu, 27 Aug 2020 12:05:18 GMT
I0827 14:05:18.579762   29736 round_trippers.go:452]     Audit-Id: d85bb70d-288a-4426-ac9a-e9a4372c3642
I0827 14:05:18.579778   29736 round_trippers.go:452]     Cache-Control: no-cache, private
I0827 14:05:18.579785   29736 round_trippers.go:452]     Content-Type: application/json
I0827 14:05:18.579790   29736 round_trippers.go:452]     X-Content-Type-Options: nosniff
I0827 14:05:18.579974   29736 round_trippers.go:423] curl -k -v -XGET  -H "X-Csrf-Token: 1" 'https://api.crc.testing:6443/.well-known/oauth-authorization-server'
I0827 14:05:18.582832   29736 round_trippers.go:443] GET https://api.crc.testing:6443/.well-known/oauth-authorization-server 200 OK in 2 milliseconds
I0827 14:05:18.582871   29736 round_trippers.go:449] Response Headers:
I0827 14:05:18.582880   29736 round_trippers.go:452]     Date: Thu, 27 Aug 2020 12:05:18 GMT
I0827 14:05:18.582886   29736 round_trippers.go:452]     Audit-Id: 1be85fc5-5a64-4fc3-9a59-10598c6ef151
I0827 14:05:18.582892   29736 round_trippers.go:452]     Cache-Control: no-cache, private
I0827 14:05:18.582897   29736 round_trippers.go:452]     Content-Type: application/json
I0827 14:05:18.582902   29736 round_trippers.go:452]     X-Kubernetes-Pf-Flowschema-Uid: 945be23f-796b-4020-8674-1e9a3d39f5e6
I0827 14:05:18.582907   29736 round_trippers.go:452]     X-Kubernetes-Pf-Prioritylevel-Uid: 3ce58648-2ee5-4df0-a945-035c4f7fe1c7
I0827 14:05:18.582912   29736 round_trippers.go:452]     Content-Length: 573
I0827 14:05:18.583102   29736 round_trippers.go:423] curl -k -v -XHEAD  'https://oauth-openshift.apps-crc.testing'
I0827 14:05:28.589597   29736 round_trippers.go:443] HEAD https://oauth-openshift.apps-crc.testing  in 10006 milliseconds
I0827 14:05:28.589629   29736 round_trippers.go:449] Response Headers:
I0827 14:05:28.592669   29736 request_token.go:448] unexpected error during system roots probe: net/http: TLS handshake timeout
I0827 14:05:28.595081   29736 round_trippers.go:423] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: odo/v0.0.0 (darwin/amd64) kubernetes/$Format" 'https://api.crc.testing:6443/api/v1/namespaces/openshift/configmaps/motd'
I0827 14:05:28.621297   29736 round_trippers.go:443] GET https://api.crc.testing:6443/api/v1/namespaces/openshift/configmaps/motd 403 Forbidden in 26 milliseconds
I0827 14:05:28.621330   29736 round_trippers.go:449] Response Headers:
I0827 14:05:28.621339   29736 round_trippers.go:452]     Content-Length: 303
I0827 14:05:28.621346   29736 round_trippers.go:452]     Date: Thu, 27 Aug 2020 12:05:28 GMT
I0827 14:05:28.621353   29736 round_trippers.go:452]     Audit-Id: b39f60fe-5750-4649-a86e-b75120e00a4a
I0827 14:05:28.621359   29736 round_trippers.go:452]     Cache-Control: no-cache, private
I0827 14:05:28.621367   29736 round_trippers.go:452]     Content-Type: application/json
I0827 14:05:28.621372   29736 round_trippers.go:452]     X-Content-Type-Options: nosniff
I0827 14:05:28.621378   29736 round_trippers.go:452]     X-Kubernetes-Pf-Flowschema-Uid: 945be23f-796b-4020-8674-1e9a3d39f5e6
I0827 14:05:28.621384   29736 round_trippers.go:452]     X-Kubernetes-Pf-Prioritylevel-Uid: 3ce58648-2ee5-4df0-a945-035c4f7fe1c7
I0827 14:05:28.622269   29736 request.go:1022] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"configmaps \"motd\" is forbidden: User \"system:anonymous\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"openshift\"","reason":"Forbidden","details":{"name":"motd","kind":"configmaps"},"code":403}
 ✗  net/http: TLS handshake timeout
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 27, 2020
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2020
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 25, 2020
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link
Collaborator

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.

@dharmit
Copy link
Member

dharmit commented Jan 28, 2021

@savonarola27 is this issue still showing up for you with latest odo and latest CRC?

@lubomben
Copy link
Author

The issue is no more present with odo v2.0.4 and crc v1.21.0

@dharmit
Copy link
Member

dharmit commented Jan 29, 2021

@savonarola27 thanks for checking and letting us know, and apologies for this not getting looked by the team ever since you opened the issue.

@lubomben
Copy link
Author

No problem. Excuse me but in the meantime I have not used the program anymore so I do not check for the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants