Skip to content

[Bug]: primary pod is not switchover when add new wal volume #5484

Closed

Description

@litaocdl

Is there an existing issue already for this bug?

  • I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

  • I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

  • I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.24.0

What version of Kubernetes are you using?

1.31

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

when primaryUpdateMethod=switchover is set, update the cluster yaml file and add a wal storage, noticed that primary pod is doing restart instead of switchover

Cluster resource

No response

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. dosubot commented on Apr 9, 2025

    @dosubot

    Hi, @litaocdl. I'm Dosu, and I'm helping the cloudnative-pg team manage their backlog. I'm marking this issue as stale.

    Issue Summary

    • Identified bug in CloudNativePG version 1.24.0.
    • Primary pod restarts instead of executing a switchover when a new WAL volume is added.
    • primaryUpdateMethod is set to switchover.
    • Issue occurs in a self-managed Kubernetes environment using kind.
    • No further comments or activity on the issue.

    Next Steps

    • Please confirm if this issue is still relevant to the latest version of the cloudnative-pg repository by commenting here.
    • If there is no response, the issue will be automatically closed in 7 days.

    Thank you for your understanding and contribution!

  2. github-actions commented on May 3, 2025

    @github-actions
    Contributor

    This issue was closed because it has been inactive for 14 days since being marked as stale.

  3. added 2 commits that reference this issue on Feb 19, 2026
    676d76e
    c8fe123
  4. added a commit that references this issue on Feb 19, 2026
    9d216d2
  5. added a commit that references this issue on Feb 20, 2026
    4a29206
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

triagePending triage

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions