Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1369851 - Registry is missing GCS backend in 3.3 puddle rpms
Registry is missing GCS backend in 3.3 puddle rpms
Status: CLOSED CURRENTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry (Show other bugs)
3.3.0
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Scott Dodson
zhou ying
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-24 10:30 EDT by Peter Schiffer
Modified: 2016-09-19 09:28 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-09-19 09:28:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1933 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3 Release Advisory 2016-09-27 09:24:36 EDT

  None (edit)
Description Peter Schiffer 2016-08-24 10:30:50 EDT
Description of problem:
I think this is a bug, as the feature should work in 3.2, based on #1332301 but it doesn't work for me in 3.3. I'm using rpms from puddle: atomic-openshift-3.3.0.22-1.git.0.be35299

$ sudo docker images | grep registry  (I'm using my own repo in gce, because the env doesn't have access to our vpn)
repo.c.ose-refarch.internal:5000/openshift3/ose-docker-registry   v3.3.0.22           95a837e68a1e        6 days ago          664 MB

$ oc logs docker-registry-2-ba12c
time="2016-08-24T09:41:47.725159072-04:00" level=info msg="version=v2.4.1+unknown" 
panic: StorageDriver not registered: gcs

goroutine 1 [running]:
panic(0x1a9eae0, 0xc8202438b0)
	/usr/lib/golang/src/runtime/panic.go:481 +0x3e6
github.com/openshift/origin/vendor/github.com/docker/distribution/registry/handlers.NewApp(0x7fb58082d880, 0x2cd1460, 0xc8203ee2c0, 0x7fb58082d880)
	/builddir/build/BUILD/atomic-openshift-git-0.be35299/_build/src/github.com/openshift/origin/vendor/github.com/docker/distribution/registry/handlers/app.go:121 +0x619
github.com/openshift/origin/pkg/cmd/dockerregistry.Execute(0x7fb580817270, 0xc820324068)
	/builddir/build/BUILD/atomic-openshift-git-0.be35299/_build/src/github.com/openshift/origin/pkg/cmd/dockerregistry/dockerregistry.go:59 +0x4d3
main.main()
	/builddir/build/BUILD/atomic-openshift-git-0.be35299/_build/src/github.com/openshift/origin/cmd/dockerregistry/main.go:51 +0x47d


config (managed by ansible and I'm using scoped vms, so that's why no keyfile):
version: 0.1
log:
  level: debug
http:
  addr: :5000
storage:
  cache:
    layerinfo: inmemory
  gcs:
    bucket: "{{ gcs_registry_bucket }}"
    rootdirectory: /registry
auth:
  openshift:
    realm: openshift
middleware:
  repository:
    - name: openshift
Comment 2 Scott Dodson 2016-08-24 14:27:10 EDT
v3.3.0.22 was prior to us using hack/build-cross.sh which injects the correct tags into the build process. Can you please re-test with v3.3.0.25.
Comment 3 zhou ying 2016-08-25 22:49:57 EDT
blocked by bug 1370045
Comment 4 zhou ying 2016-08-28 23:11:24 EDT
Confirmed with latest openshift puddle, the issue has fixed:
openshift version
openshift v3.3.0.26
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

more /etc/registryconfig/config.yml
version: 0.1
log:
  level: debug
http:
  addr: :5000
storage:
  cache:
    layerinfo: inmemory
  gcs:
    bucket: ose-qe-docker-registry
    keyfile: /etc/registryconfig/key.json
    rootdirectory: /registry-20160828211232
auth:
  openshift:
    realm: openshift
middleware:
  repository:
    - name: openshift
      options:
        pullthrough: true
  registry:
     - name: openshift
  storage:
     - name: openshift
Comment 5 Peter Schiffer 2016-08-31 08:11:46 EDT
This works for me now with:
atomic-openshift-3.3.0.27-1.git.0.f1694b3.el7.x86_64

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