Bug 1309258

Summary: With the user token can't login the integrated registry with docker 1.9
Product: OKD Reporter: zhou ying <yinzhou>
Component: Image RegistryAssignee: Michal Minar <miminar>
Status: CLOSED NOTABUG QA Contact: Wei Sun <wsun>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 07:56:58 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:
Embargoed:

Description zhou ying 2016-02-17 10:35:08 UTC
Description of problem:
After login OpenShift, try to login the integrated registry with the user token will meet error.


Version-Release number of selected component (if applicable):
openshift v3.1.1.902
kubernetes v1.2.0-origin
etcd 2.2.2+git
docker 1.9

How reproducible:
always

Steps to Reproduce:
1. Login OpenShift;
2. Get the user token:
  `oc whoami -t`
3. Use the user token to login integrated registry:
 `docker login -u yinzhou -p NlPIqt2SY1B9uIgpfYdCsHQQ-MiCYBItrafunLfVGjo -e yinzhou 172.31.251.67:5000`

Actual results:
Login failed, with error:
Error response from daemon: invalid registry endpoint https://172.31.251.67:5000/v0/: unable to ping registry endpoint https://172.31.251.67:5000/v0/
v2 ping attempt failed with error: Get https://172.31.251.67:5000/v2/: Forbidden
 v1 ping attempt failed with error: Get https://172.31.251.67:5000/v1/_ping: Forbidden. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry 172.31.251.67:5000` to the daemo
n's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/172.31.251.67:5000/ca.crt

Expected results:
Login successfully.

Additional info:
With docker 1.8 will login successfully

Comment 1 zhou ying 2016-02-18 07:56:58 UTC
Use the command on wrong host, so not a bug.