Description of problem (please be detailed as possible and provide log snippests): There is a lot of MongoNetworkError error messages in noobaa-core pod logs. Version of all relevant components (if applicable): ocs-operator.v4.7.0-238.ci ocp 4.7.0-0.nightly-2021-01-27-072811 Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? yes Steps to Reproduce: 1. oc logs <noobaa-core pod> -n openshift-storage | grep MongoNetworkError Actual results: There are error messages like: [HostedAgents/74148] [ERROR] core.util.mongo_client:: _connect: initial connect failed, will retry MongoNetworkError: failed to connect to server [noobaa-db-0.noobaa-db:27017] on first connect [Error: getaddrinfo ENOTFO UND noobaa-db-0.noobaa-db Expected results: There are no MongoDB related messages when PostgreSQL is used. Additional info: cluster had enabled kms integration but it seems to not be relevant
Looks ok. --> VERIFIED Tested with: ocs-operator.v4.7.0-257.ci
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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2021:2041