Skip to content

Conversation

@idanovinda
Copy link
Member

When operator (re)-start, c.currentMajorVersion will be 0. This value will be updated only if we execute majorVersionUpgrade until the part where we get the current version from the Patroni. In #2727, we skipped the part where we do update this value when a cluster have last-major-upgrade-failure annotation. Hence, this cluster will never update its c.currentMajorVersion after operator restarts and will always be 0. Our e2e test couldn't catch this as we test the last-major-upgrade-failure after doing some upgrades.

Solution

We should only skip the upgrade of the failure upgrade only after we make sure that the recheck is done.

@idanovinda
Copy link
Member Author

👍

1 similar comment
@FxKu
Copy link
Member

FxKu commented Sep 10, 2024

👍

@idanovinda idanovinda merged commit c25dc57 into master Sep 10, 2024
@idanovinda idanovinda deleted the bugfix/major-upgrade-check branch September 10, 2024 08:32
@FxKu FxKu added this to the 1.14.0 milestone Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants