Issues
- Error while creating backup: failed to find CERTIFICATEK8SPSMDB-1263Eleonora Zinchenko
- Unexposing replicaset nodes breaks MongoDB clusterK8SPSMDB-1068Resolved issue: K8SPSMDB-1068
- Checking authorization failed errors in Mongo LogsK8SPSMDB-1058Resolved issue: K8SPSMDB-1058Pavel Tankov
- Change operator container port for metrics to 8080K8SPSMDB-1033Resolved issue: K8SPSMDB-1033Tomislav Plavcic
- Helm chart - add serviceAccountName to the existing resourcesK8SPSMDB-997Resolved issue: K8SPSMDB-997Tomislav Plavcic
- Do not start backups if storages or credentials are not set.K8SPSMDB-976Resolved issue: K8SPSMDB-976
- Restore fails with dup key on admin.pbmBackupsK8SPSMDB-975Resolved issue: K8SPSMDB-975
- missing info on external node being added/removed to replica setK8SPSMDB-964
- votes and priority are mandatory when specifying external nodesK8SPSMDB-963Resolved issue: K8SPSMDB-963
- Percona Operator POD constantly increasing CPU and Memory usageK8SPSMDB-962Resolved issue: K8SPSMDB-962Andrii Dema
- PMM fails to monitor mongoS due to lack of permission.K8SPSMDB-958Resolved issue: K8SPSMDB-958
- Certificate Rotation brought the Sharded MongoDB cluster downK8SPSMDB-956Resolved issue: K8SPSMDB-956
- Detect k8s cluster domain automatically instead of using cluster.local blindlyK8SPSMDB-954ege.gunes
- MongoDB clusters keep failing with ReplicaSetNoPrimaryK8SPSMDB-953Resolved issue: K8SPSMDB-953
- Cross-site replication unstable through too many reconcile connectionsK8SPSMDB-949Resolved issue: K8SPSMDB-949
- Support ARM for operator and percona replicasK8SPSMDB-948Resolved issue: K8SPSMDB-948dmitriy.kostiuk
- PSMDB operator is not working with Linkerd service meshK8SPSMDB-945
- Scheduled backups aren't deleted, pitr is not continuousK8SPSMDB-944Aaditya Dubey
- Default resource limits cause instability and crash loops with moderate datasetK8SPSMDB-936
- Helm chart - watchNamespace doesn't workK8SPSMDB-930Resolved issue: K8SPSMDB-930Tomislav Plavcic
- Can't connect to MongoDB Replica Set via LoadBalancerK8SPSMDB-929Resolved issue: K8SPSMDB-929
- Support ClusterIssuer for MongoDB ReplicaSet Cluster with TLS and Let's EncryptK8SPSMDB-928
- make cronjob less verboseK8SPSMDB-924Resolved issue: K8SPSMDB-924
- IRSA is not enabled for restoreK8SPSMDB-921Resolved issue: K8SPSMDB-921dmitriy.kostiuk
- restore recreates mongos pod which recreates load balancerK8SPSMDB-913Resolved issue: K8SPSMDB-913
- Fix mongod-major-upgrade-sharded testK8SPSMDB-909Resolved issue: K8SPSMDB-909Tomislav Plavcic
- Update Supported k8s Versions per Operator versionsK8SPSMDB-908
- Helm chart - add affinityAdvanced optionK8SPSMDB-905Resolved issue: K8SPSMDB-905Tomislav Plavcic
- Update operator with latest PBM and PSMDB distribution releasesK8SPSMDB-902Resolved issue: K8SPSMDB-902Tomislav Plavcic
- PerconaServerMongoDBRestore failed with this error [WT_VERB_EXTENSION][ERROR]: libcrypto: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:crypto/evp/evp_enc.c:643K8SPSMDB-898dmitriy.kostiuk
- Can't install Percona Server for MongoDB on MinikubeK8SPSMDB-896Resolved issue: K8SPSMDB-896dmitriy.kostiuk
- Helm - Add pod/container security context for operatorK8SPSMDB-890Resolved issue: K8SPSMDB-890Tomislav Plavcic
- PSMDB operator 1.14.0 - CustomResourceDefinition "perconaservermongodbs.psmdb.percona.com" is invalidK8SPSMDB-887Resolved issue: K8SPSMDB-887
- E2E tests - start mongod major upgrade from the lowest versionK8SPSMDB-885Resolved issue: K8SPSMDB-885Tomislav Plavcic
- encryptionKey secret is created even if encryption is disabledK8SPSMDB-884
- Remove mongod section from CRK8SPSMDB-883Resolved issue: K8SPSMDB-883
- React on backup/restore error inside e2e testing frameworkK8SPSMDB-881Resolved issue: K8SPSMDB-881Ivan Pylypenko
- name for mongos poddistruptionbudget looks unfinishedK8SPSMDB-879
- upgrade-consistency test is failingK8SPSMDB-878Resolved issue: K8SPSMDB-878
- delete-psmdb-pods-in-order finalizer doesn't affect config replica setK8SPSMDB-876Resolved issue: K8SPSMDB-876
- cannot run physical restores with non-voting/arbiter/delayed replica membersK8SPSMDB-875Resolved issue: K8SPSMDB-875
- Mongosh breaks ps-entry.sh logic on OpenshiftK8SPSMDB-873Resolved issue: K8SPSMDB-873inel.pandzic
- operator should not try to restore backup with error statusK8SPSMDB-872Resolved issue: K8SPSMDB-872
- delete backup finalizer fails with PBM v2 with old storageK8SPSMDB-845Resolved issue: K8SPSMDB-845Andrii Dema
- Fix e2e tests for PBM 2.xK8SPSMDB-821Resolved issue: K8SPSMDB-821Tomislav Plavcic
45 of 45
Error while creating backup: failed to find CERTIFICATE
General
Escalation
General
Escalation
Description
Environment
mongodb_version: 6.0.9-7
pbm_version: 2.3.0
percona-server-mongodb-operator:1.15.0
AFFECTED CS IDs
CS0052379
Created January 20, 2025 at 9:04 AM
Updated March 12, 2025 at 1:30 PM
Activity
ege.gunesMarch 3, 2025 at 8:55 AM
Unfortunately I can't reproduce this bug but I'm fairly sure that this will be fixed with https://perconadev.atlassian.net/browse/K8SPSMDB-1276 and https://github.com/percona/percona-server-mongodb-operator/pull/1736
radoslaw.szulgoFebruary 27, 2025 at 6:46 PM
It's from the community forum. You may ask there.
While creating a normal logical backup of a 1.3TB replica, its state changes to errored after about 16 hours of run with the following:
check for concurrent jobs: getting pbm object: create PBM connection to mongo-rs0-2.mongo-rs0.mongo.svc.cluster.local:27017,mongo-rs0-0.mongo-rs0.mongo.svc.cluster.local:27017,mongo-rs0-1.mong-rs0.mongo.svc.cluster.local:27017: create mongo connection: create mongo client: failed to find CERTIFICATEThe backup job however still progresses and completes, but I’m unsure as to the validity of the backup it creates (and the fact that I doubt it’s possible to restore from that unless manually changing its status to success)
Affected: 1.13.0, 1.14.0, 1.15.0 and probable further versions
See also Community forum thread: https://forums.percona.com/t/error-while-creating-backup-failed-to-find-certificate/23101/12