Description of problem:

After creating MongoDB Ops Manager, it's failing with due to lack of permissions on volume:

Using property mms.centralUrl=http://ops-manager-svc.mongodb.svc.cluster.local:8080
Using property mms.fromEmailAddr=admin@thecompany.com
Using property mms.managedAppDb=true
Using property mms.temp.appDb.version=4.0.9
Using property mongo.mongoUri=mongodb://ops-manager-db-0.ops-manager-db-svc.mongodb.svc.cluster.local,ops-manager-db-1.ops-manager-db-svc.mongodb.svc.cluster.local,ops-manager-db-2.ops-manager-db-svc.mongodb.svc.cluster.local/?connectTimeoutMS=15000&serverSelectionTimeoutMS=15000
Starting Ops Manager...
Checking the Application Database
chown: changing ownership of '/opt/mongodb/mms/logs/mms0.log': Operation not permitted
[FAILED]
Check /opt/mongodb/mms/logs/mms0.log for errors
Startup of Ops Manager failed with code 1

CR Definition:
apiVersion: mongodb.com/v1
kind: MongoDBOpsManager
metadata:
name: ops-manager
namespace: mongodb
spec:
adminCredentials: ops-manager-admin-secret
applicationDatabase:
members: 3
persistent: true
podSpec:
cpu: '1'
type: ReplicaSet
version: 4.2.0
configuration:
mms.fromEmailAddr: admin@thecompany.com
version: 4.2.0

The same behavior occurs if I change persistent to false

Version-Release number of selected component (if applicable):

oc get pod ops-manager-0 -o yaml | grep image:
image: quay.io/mongodb/mongodb-enterprise-ops-manager:4.2.0
image: quay.io/mongodb/mongodb-enterprise-ops-manager:4.2.0

MongoDB Operator: 1.2.4
OCP Cluster: 4.3.0-0.nightly-2019-11-07-062654

How reproducible: Always

Steps to Reproduce:
1. Install MongoDB Operator
2. Create ops-manager-admin-secret
3. Create MongoDB Ops Manager

Actual results:
MongoDB Ops Manager is failing due to permission issues at volume

Expected results:
MongoDB Ops Manager should run without any issue.

Additional info: