Bug 1466035

Summary: Registry health checks fail with error http2: no cached connection was available
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: NodeAssignee: Derek Carr <decarr>
Status: CLOSED DUPLICATE QA Contact: DeShuai Ma <dma>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: aos-bugs, bandrade, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-28 20:16:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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):

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 http2: no cached connection was available

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

Expected results:

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

Additional info:

Possible upstream issue: 


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