Bug 1292541 - Upgrading from 3.0 to 3.1 with a secured registry causes error with registry
Summary: Upgrading from 3.0 to 3.1 with a secured registry causes error with registry
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-17 17:49 UTC by Ryan Howe
Modified: 2019-09-12 09:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-13 16:26:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Howe 2015-12-17 17:49:19 UTC
Description of problem:Upgrading from 3.0 to 3.1 with a secured registry causes error with registry. 


docker registry 2015-12-15 19:33:57.452369 I | http: TLS handshake error from 10.1.2.1:53313: EOF



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


How reproducible:
Have not reproduced


Steps to Reproduce:
1. Upgrade a 3.0 ose to 3.1 with a registry that is secured
2. openssl x509 -in /etc/origin/node/server.crt -text -noout | grep -A 1 "Subject Alternative Name" 

-- Shows only hostname of node

3. During upgrade certs were not remade 
4. Redeploy registry with 3.1 image



Actual results:
Error  docker registry 2015-12-15 19:33:57.452369 I | http: TLS handshake error from 10.1.2.1:53313: EOF

Expected results:
Should work as it did in 3.0.2


Additional info:

To fix we went through and removed the following 

$ oc volume dc/docker-registry --remove --name=registry-secret 
$ oc env dc/docker-registry REGISTRY_HTTP_TLS_CERTIFICATE-
$ oc env dc/docker-registry REGISTRY_HTTP_TLS_KEY-

Then added insecure registry back to the the /etc/sysconfig/docker

Comment 2 Anping Li 2016-01-08 10:41:35 UTC
I have upgraded v3.0.2 with secured registry to both v3.1.0.4(Release Version) and (v3.1.1.0), and after upgrade the registry works fine. Maybe the error isn't caused by upgrade.

Comment 3 Anping Li 2016-01-13 08:18:44 UTC
Ryan, QE can't reproduced this issue. Could you provide more information about this bug. How do you create security registry?  How do you upgrade from 3.0 to 3.1?
I see your set 'Have not reproduced'.  I am thinking that is caused by other component rather than 'upgrade"?


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