Skip to content

increasing pvc size with enableVolumeExpansion in PSA setup is broken #2051

@KyriosGN0

Description

@KyriosGN0

Report

we have several mongodb deployed on k8s with the percona operator, when setting enableVolumeExpansion: true and using the PSA setup, we have found that after the disk expansion is successful, the secondary is removed from the replicaset and cannot be added back by the operator

More about the problem

after the secondary is removed we see operator erroring with these logs
reconcile statefulsets: failed to update config members: add new: write mongo config: replSetReconfig: (NewReplicaSetConfigurationIncompatible) Rejecting reconfig where the new config has a PSA topology and the secondary is electable, but the old config contains only one writable node. Refer to https://docs.mongodb.com/manual/reference/method/rs.reconfigForPSASet/ for next steps on reconfiguring a PSA set

Steps to reproduce

  1. set enableVolumeExpansion on a PSA (1P, 1S, 1A) db
  2. increase the storage size

Versions

  1. Kubernetes 1.32
  2. Operator 1.20.1
  3. Database. mongodb 7

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions