| Summary: | Registry fails to start in 3.2.1.17 - no storage middleware registered with name: openshift | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vladislav Walek <vwalek> |
| Component: | Image Registry | Assignee: | Michal Fojtik <mfojtik> |
| Status: | CLOSED DUPLICATE | QA Contact: | Wei Sun <wsun> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.1 | CC: | aos-bugs, pep |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-21 10:53:07 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: | |
*** This bug has been marked as a duplicate of bug 1386674 *** |
Description of problem: After the installation, the registry fails with the error : panic: unable to configure storage middleware (openshift): no storage middleware registered with name: openshift oc logs docker-registry-<uniqid> panic: unable to configure storage middleware (openshift): no storage middleware registered with name: openshift goroutine 1 [running]: github.com/docker/distribution/registry/handlers.NewApp(0x7fa39b877098, 0x225a720, 0xc20835c280, 0x7fa39b877098) /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_thirdpartyhacks/src/github.com/docker/distribution/registry/handlers/app.go:134 +0xd68 github.com/openshift/origin/pkg/cmd/dockerregistry.Execute(0x7fa39b869900, 0xc20802c680) /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_build/src/github.com/openshift/origin/pkg/cmd/dockerregistry/dockerregistry.go:60 +0x4d0 main.main() /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_build/src/github.com/openshift/origin/cmd/dockerregistry/main.go:51 +0x3ea goroutine 5 [chan receive]: github.com/golang/glog.(*loggingT).flushDaemon(0x225b180) /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_thirdpartyhacks/src/github.com/golang/glog/glog.go:879 +0x78 created by github.com/golang/glog.init·1 /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_thirdpartyhacks/src/github.com/golang/glog/glog.go:410 +0x2a7 goroutine 17 [syscall, locked to thread]: runtime.goexit() /usr/lib/golang/src/runtime/asm_amd64.s:2232 +0x1 goroutine 13 [syscall]: os/signal.loop() /usr/lib/golang/src/os/signal/signal_unix.go:21 +0x1f created by os/signal.init·1 /usr/lib/golang/src/os/signal/signal_unix.go:27 +0x35 goroutine 20 [runnable]: github.com/docker/distribution/registry/handlers.func·009() /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_thirdpartyhacks/src/github.com/docker/distribution/registry/handlers/app.go:964 created by github.com/docker/distribution/registry/handlers.startUploadPurger /builddir/build/BUILD/atomic-openshift-git-0.6d01b60/_thirdpartyhacks/src/github.com/docker/distribution/registry/handlers/app.go:975 +0x942 Same issue was reported in: https://bugzilla.redhat.com/show_bug.cgi?id=1355885 https://bugzilla.redhat.com/show_bug.cgi?id=1353830 In last BZ is stated that the issue was fixed in 3.2.1.6, but customer is running version 3.2.1.17 (registry and version) Issue only occurs on registry (router is running normally). In 3.3 https://bugzilla.redhat.com/show_bug.cgi?id=1353804 it seems to be fixed in v3.3.0.4 We found with customer that 3.2.1.9 is working as it should the problem is fixed there, but the 3.2.1.17 has the same issue as in bugs above. Could be also in previous version from 3.2.1.17. Thanks Vladislav