Hide Forgot
Description of problem: Update the mongodb-cluster.json to use the rhel based image will cause the pod cannot startup Version-Release number of selected component (if applicable): mongodb-24-rhel7 mongodb-26-rhel7 mongodb-32-rhel7 How reproducible: always Steps to Reproduce: 1.wget https://raw.githubusercontent.com/openshift/mongodb/master/2.4/examples/replica/mongodb-clustered.json 2.replace the image with mongodb-24-rhel7 3.oc new-app mongodb-cluster.json Actual results: pod cannot startup with error : /usr/bin/container-entrypoint: line 2: exec: run-mongod-replication: not found Expected results: pod should startup successfully Additional info:
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.