Red Hat Bugzilla – Bug 1292541
Upgrading from 3.0 to 3.1 with a secured registry causes error with registry
Last modified: 2016-01-13 11:26:03 EST
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
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
Error docker registry 2015-12-15 19:33:57.452369 I | http: TLS handshake error from 10.1.2.1:53313: EOF
Should work as it did in 3.0.2
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
I have upgraded v3.0.2 with secured registry to both v220.127.116.11(Release Version) and (v18.104.22.168), and after upgrade the registry works fine. Maybe the error isn't caused by upgrade.
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"?