| Summary: | mongodb cluster template cannot start up with rhel image | ||
|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Wang Haoran <haowang> |
| Component: | rh-mongodb32-container | Assignee: | Marek Skalický <mskalick> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | qe-baseos-daemons |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | devassist09 | CC: | aos-bugs, bparees, jokerman, mmccomas, trepik |
| 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: | 2017-04-12 14:31:05 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: | |
|
Description
Wang Haoran
2016-10-18 02:42:39 UTC
Pulling the latest images from the Red Hat registry I could reproduce the problem.
Steps:
$ docker pull registry.access.redhat.com/rhscl/mongodb-32-rhel7
...
Digest: sha256:e5b2a229b8376ca128c552b36534be349b932c791273c739949f67b57b8d4ceb
Status: Downloaded newer image for registry.access.redhat.com/rhscl/mongodb-32-rhel7:latest
$ docker inspect -f '{{.Id}}' registry.access.redhat.com/rhscl/mongodb-32-rhel7
sha256:4856466a44d50063c9c2fba5e61a6b7cfaaafd325a0c62eca564ca382ac03c83
$ docker run --rm -it registry.access.redhat.com/rhscl/mongodb-32-rhel7 run-mongod-replication
/usr/bin/container-entrypoint: line 2: exec: run-mongod-replication: not found
The `run-mongod-replication` script was introduced in https://github.com/sclorg/mongodb-container/pull/177.
That PR was merged in Sep 13, looks like we're missing a more timely rebuild of the RHEL images.
A rebuild should fix the problem.
Re-assigning to SCL team who owns the image and can do the rebuild.
This issue is already fixed. So closing this bug. |