Bug 1315948
Summary: | [platformmanagement_public_595]When use the S3 as the integrated docker-registry storage can't push or pull images successfully | ||
---|---|---|---|
Product: | OKD | Reporter: | zhou ying <yinzhou> |
Component: | Image Registry | Assignee: | Michail Kargakis <mkargaki> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wei Sun <wsun> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.x | CC: | aos-bugs, pweil, yinzhou |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 17:12:16 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-03-09 05:38:19 UTC
"6. Tag a ImageStream; `oc tag docker.io/zhouying7780/hello-test hellotest:v1` 7. Docker login the integrated docker-registry by the user token; 8. Try to pull the image by command: `docker pull 172.30.239.9:5000/zhouy/hellotest:v1`" This is not related to S3 and is https://github.com/openshift/origin/issues/7792. Can you please post the output of `oc logs build/<name-of-your-build> --tail 6`? Only the last line is not enough. Also are you running OpenShift locally or in a EC2 instance? Actually nevermind about the oc logs command. I think I have just reproduced this. Looking... Can you post the output of `oc logs dc/docker-registry` after you see the 500 error? It would be really helpful to debug this. I can confirm that docker push is working against our registry backed with S3. http://pastebin.com/iVxMZEuk You most probably see the 500 due to wrong credentials (why I was seeing 500). Michail, Thanks, I've confirmed with ami devenv_rhel_3734, in config.yml, the bucket should be like this: bucket: openshift-qe-registry-testing-bucket1 now the issue has fixed. [root@ip-172-18-11-61 amd64]# openshift version openshift v1.1.4-16-gb5da002 kubernetes v1.2.0-origin-41-g91d3e75 etcd 2.2.5 [root@ip-172-18-11-61 amd64]# docker tag -f busybox 172.30.22.13:5000/zhouy/stream:v122 [root@ip-172-18-11-61 amd64]# docker push 172.30.22.13:5000/zhouy/stream:v122 The push refers to a repository [172.30.22.13:5000/zhouy/stream] (len: 1) 559d41a5eba1: Pushed bb2571406a55: Pushed v122: digest: sha256:c0aa37999df88fa0b7c4f4035f4e77d54469b30476d0fb6c4d5206b65eced788 size: 2734 [root@ip-172-18-11-61 amd64]# docker exec -it 0830b81503a5 more /config/config.yml version: 0.1 log: level: debug http: addr: :5000 storage: cache: layerinfo: inmemory version: 0.1 log: level: debug http: addr: :5000 storage: cache: layerinfo: inmemory s3: accesskey: xxxxxxxxxxx secretkey: yyyyyyyyyyyyyyyyyyyyyyy region: us-east-1 bucket: openshift-qe-registry-testing-bucket1 encrypt: true secure: true v4auth: false rootdirectory: /registry auth: openshift: realm: openshift middleware: repository: - name: openshift options: pullthrough: true |