Closed jam13 closed 7 years ago
If you make this call against the API, you'll see the problem:
curl -v -N -H "Authorization: Bearer xxxxxxxx" \
https://openshift.example.com/oapi/v1/namespaces/myproject/routes/?watch&labelSelector=butter.sh/letsencrypt-managed=yes
after about 60 seconds I see:
* transfer closed with outstanding read data remaining
* Closing connection 0
curl: (18) NSS: client certificate not found (nickname not specified)
Sorry, I missed your bug report.
Unfortunately I cannot reproduce the problem. Is there a proxy between openshift.example.com and 172.30.0.1 (or whatever openshift.default
is)? Maybe that one is closing the connection.
I assume (from the logs above) that it also happens when getting using 172.30.0.1, but can you please confirm? Please also test (if you have access) on the nodes itself: on the master node (where origin-master is running) and any other node.
I think this is probably only with Openshift 1.5. Changing the call from watch to watch=true (which is the documented form) solved the problem.
My watcher container always dies and respawns after running for 2 minutes.
The problem seems to be with curl making api calls to the routes resource. It receives data but then after 60 seconds it times out thinking there is outstanding read data. The second (debugging?) curl call does the same thing, giving a total of 2 minutes.
Here's an example trace with curl running verbose: