Uploaded image for project: 'Percona Operator for MongoDB'
  1. Percona Operator for MongoDB
  2. K8SPSMDB-721

Backup container failing takes down database pod

Details

    • Improvement
    • Status: Done
    • Medium
    • Resolution: Fixed
    • 1.12.0
    • 1.14.0
    • None
    • None
    • Yes
    • Yes

    Description

      If the pbm-agent sidecar for some reason cannot connect to MongoDB, the pod never gets to "ready" state, and CrashLoopBackOff ensues.

      For example, if password is misconfigured in secrets this happens.

            name: backup-agent
            ready: false
            restartCount: 870
            started: false
            state:
              waiting:
                message: back-off 5m0s restarting failed container=backup-agent pod=percona-mongo-psmdb-d-rs1-1_data(f8278e2e-dc5f-4499-9de9-7c836d73a1a0)
                reason: CrashLoopBackOff

      It might be better to have the database working, even if backups fail. Or perhaps current behavior is intentional? 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sami.ahlroos Sami Ahlroos
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Smart Checklist