Description of problem: Create app via "oc new-app mongodb-persistent" in OpenShift 4 cluster, the output show it use version 3.6, while it points to 3.2 doc Version-Release number of selected component (if applicable): 3.6 How reproducible: Always Steps to Reproduce: 1. oc new-app mongodb-persistent Actual results: $ oc new-app mongodb-persistent --> Deploying template "openshift/mongodb-persistent" to project lxiap MongoDB --------- MongoDB database service, with persistent storage. For more information about using this template, including OpenShift considerations, see https://github.com/sclorg/mongodb-container/blob/master/3.2/README.md. NOTE: Scaling to more than one replica is not supported. You must have persistent volumes available in your cluster to use this template. The following service(s) have been created in your project: mongodb. Username: userFGE Password: MrCux6tsjgUusbsH Database Name: sampledb Connection URL: mongodb://userFGE:MrCux6tsjgUusbsH@mongodb/sampledb For more information about using this template, including OpenShift considerations, see https://github.com/sclorg/mongodb-container/blob/master/3.2/README.md. * With parameters: * Memory Limit=512Mi * Namespace=openshift * Database Service Name=mongodb * MongoDB Connection Username=userFGE # generated * MongoDB Connection Password=MrCux6tsjgUusbsH # generated * MongoDB Database Name=sampledb * MongoDB Admin Password=7G4LjuxEc7fLf1Ij # generated * Volume Capacity=1Gi * Version of MongoDB Image=3.6 --> Creating resources ... secret "mongodb" created service "mongodb" created persistentvolumeclaim "mongodb" created deploymentconfig.apps.openshift.io "mongodb" created --> Success Application is not exposed. You can expose services to the outside world by executing one or more of the commands below: 'oc expose svc/mongodb' Run 'oc status' to view your app. Expected results: The version used and docs should be consistent. Additional info:
Makes sense, we should not be pointing to any version of the image's README in the template descrition. It should instead be a link to the upstream repository or the root README, from where the user can find the README version he needs. Will need to be fixed upstream first, then synced into Openshift. Will move the BZ back tot he Openshift component once the upstream PR is merged.
Upstream PR: https://github.com/sclorg/mongodb-container/pull/307
Merged upstream, moving back to the Openshift product.
openshift/library commit picking up upstream: [afed941](https://github.com/openshift/library/commit/afed94135f0cc786f34ea97877ac9e32a87f2ba1#diff-1f504069b04966195f614511871d5ca8) PR for samples-operator: https://github.com/openshift/cluster-samples-operator/pull/149
Mark this bug as verified with 4.2.0-0.ci-2019-06-16-194145
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922