Bug 1466035 - Registry health checks fail with error http2: no cached connection was available
Summary: Registry health checks fail with error http2: no cached connection was available
Keywords:
Status: CLOSED DUPLICATE of bug 1454858
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 19:40 UTC by Ryan Howe
Modified: 2020-08-13 09:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-28 20:16:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ryan Howe 2017-06-28 19:40:25 UTC
Description of problem:

 Randomly one of the health checks on the registry fails. 


Version-Release number of selected component (if applicable):
OCP 3.5.5.8

How reproducible:
Happens intermittently 

Actual results:

 atomic-openshift-node[36648][prober.go:106] Readiness probe for "docker-registry-12-lknh8_default(91642388-5c0a-11e7-9c80-005056961e9a):registry" failed (failure): Get https://10.1.4.60:5000/healthz: http2: no cached connection was available

 dockerd-current[1501]: 10.1.4.1 - - [28/Jun/2017:17:17:01 +0000] "GET /healthz HTTP/2.0" 200 0 "" "Go-http-client/2.0"

Expected results:

 dockerd-current[1501]: 10.1.4.1 - - [28/Jun/2017:17:17:11 +0000] "GET /healthz HTTP/2.0" 200 0 "" "Go-http-client/2.0"
 dockerd-current[1501]: 10.1.4.1 - - [28/Jun/2017:17:17:11 +0000] "GET /healthz HTTP/2.0" 200 0 "" "Go-http-client/2.0"


Additional info:

Possible upstream issue: 

  https://github.com/golang/go/issues/16582
  https://github.com/golang/go/commit/7a622740655bb5fcbd160eb96887032314842e6e

Comment 2 Derek Carr 2017-06-28 20:16:05 UTC

*** This bug has been marked as a duplicate of bug 1454858 ***

Comment 3 Derek Carr 2017-06-28 20:16:34 UTC
See: https://bugzilla.redhat.com/show_bug.cgi?id=1454858#c2


Note You need to log in before you can comment on or make changes to this bug.