erro in ops manager when deploy on openshift

this is the ops manager CRD

apiVersion: mongodb.com/v1
kind: MongoDBOpsManager
metadata:
  annotations:
    mongodb.com/v1.lastAppliedMongoDBVersion: 7.0.11
  creationTimestamp: '2024-06-04T09:25:47Z'
  generation: 7
  managedFields:
    - apiVersion: mongodb.com/v1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:mongodb.com/v1.lastAppliedMongoDBVersion': {}
      manager: mongodb-enterprise-operator
      operation: Update
      time: '2024-06-04T10:56:27Z'
    - apiVersion: mongodb.com/v1
      fieldsType: FieldsV1
      fieldsV1:
        'f:spec':
          .: {}
          'f:adminCredentials': {}
          'f:applicationDatabase':
            'f:topology': {}
            'f:version': {}
            'f:members': {}
            'f:credentials': {}
            'f:clusterDomain': {}
            'f:podSpec': {}
            .: {}
            'f:type': {}
            'f:logLevel': {}
          'f:clusterDomain': {}
          'f:replicas': {}
          'f:topology': {}
          'f:version': {}
      manager: Mozilla
      operation: Update
      time: '2024-06-04T11:05:49Z'
    - apiVersion: mongodb.com/v1
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          .: {}
          'f:applicationDatabase':
            .: {}
            'f:clusterStatusList': {}
            'f:lastTransition': {}
            'f:members': {}
            'f:message': {}
            'f:observedGeneration': {}
            'f:phase': {}
            'f:version': {}
          'f:opsManager':
            .: {}
            'f:lastTransition': {}
            'f:message': {}
            'f:observedGeneration': {}
            'f:phase': {}
            'f:resourcesNotReady': {}
            'f:url': {}
      manager: mongodb-enterprise-operator
      operation: Update
      subresource: status
      time: '2024-06-04T11:15:30Z'
  name: ops-manager
  namespace: mongo-operator
  resourceVersion: '11032339'
  uid: 986398d2-db93-4908-b9e9-f4456b5e3562
spec:
  adminCredentials: ops-manager-admin-pass
  applicationDatabase:
    clusterDomain: itvalley.local
    credentials: ops-manager-admin-pass
    logLevel: DEBUG
    members: 3
    podSpec: {}
    topology: SingleCluster
    type: Standalone
    version: 7.0.11
  clusterDomain: itvalley.local
  replicas: 1
  topology: SingleCluster
  version: 7.0.6
-------------------------------------------
and that the error that we faced in ops manager pod 
-------------------------------------------------------------------
The /mongodb-ops-manager/conf directory is not empty. Skipping copying files from /mongodb-ops-manager/conf-template
This might cause errors when booting up the OpsManager with read-only root filesystem
Updating configuration properties file /mongodb-ops-manager/conf/conf-mms.properties and conf file /mongodb-ops-manager/conf/mms.conf
Appending JAVA_MMS_UI_OPTS="${JAVA_MMS_UI_OPTS} -Xmx4291m -Xms4291m" to /mongodb-ops-manager/conf/mms.conf
Updating configuration properties file /mongodb-ops-manager/conf/conf-mms.properties
Starting Ops Manager
Starting pre-flight checks
Failure to connect to configured mongo instance: Config{loadBalance=false, encryptedCredentials=false, ssl='false', dbNames='[atlasbackup, mmsdbautomation, mmsdbserverlog, mmsdbpings, monitoringdiagnostics, mmsdbprofile, mmsdbjobs, realmdiscovery, oa, agentlogs, mmsdbftsrrd, automationcore, monitoringstatus, automationstatus, mmsdbrealmrrd, mmsdbserverlessrrd, chartsmetadata, authz, mmsdbprovisionlog, mmsdb, fts, platformdiagnostics, mmsdbcollstatslatencyconfig, mmsrt, mmsdbrrd, mmsdbcollstatslatencyrrd, adl, mmsdbconfig, mmsdblogcollection, mongologsmetadata, backupusage, mmsdbagentlog, monitoringftstelemetry, mmsdbbilling, backuplogs, backupstatus, mmsdbmetering, mmsdbautomationlog, ndsstatus, cloudconf, backupdb, nds, mmsdbqueues, mmsdbprovisioning]', uri=mongodb://redacted-credentials@ops-manager-db-0.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017,ops-manager-db-1.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017,ops-manager-db-2.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017/?authMechanism=SCRAM-SHA-256&authSource=admin&connectTimeoutMS=20000&replicaSet=ops-manager-db&serverSelectionTimeoutMS=20000} Error: Timed out after 20000 ms while waiting for a server that matches com.mongodb.client.internal.MongoClientDelegate$$Lambda$285/0x00007f1d7c2b7228@7981963f. Client view of cluster state is {type=REPLICA_SET, servers=[{address=ops-manager-db-0.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException: ops-manager-db-0.ops-manager-db-svc.mongo-operator.svc.itvalley.local}, caused by {java.net.UnknownHostException: ops-manager-db-0.ops-manager-db-svc.mongo-operator.svc.itvalley.local}}, {address=ops-manager-db-1.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException: ops-manager-db-1.ops-manager-db-svc.mongo-operator.svc.itvalley.local}, caused by {java.net.UnknownHostException: ops-manager-db-1.ops-manager-db-svc.mongo-operator.svc.itvalley.local}}, {address=ops-manager-db-2.ops-manager-db-svc.mongo-operator.svc.itvalley.local:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException: ops-manager-db-2.ops-manager-db-svc.mongo-operator.svc.itvalley.local}, caused by {java.net.UnknownHostException: ops-manager-db-2.ops-manager-db-svc.mongo-operator.svc.itvalley.local}}]
Pre-flight checks failed. Service can not start.
Preflight check failed.
Startup of Ops Manager failed with code 1