Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip service packs in upgrade path detection #176

Merged
merged 1 commit into from
Mar 16, 2022

Conversation

spilchen
Copy link
Collaborator

The upgrade path detection that was added in v1.3.0 of the operator was too strict when it came to checking for service packs. As per the Vertica docs, those can be skipped when doing upgrades. This PR fixes that bug.

@spilchen spilchen requested a review from roypaulin March 15, 2022 14:08
@spilchen spilchen self-assigned this Mar 15, 2022
Copy link
Collaborator

@roypaulin roypaulin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. Do you mind telling me more about what service packs are?

@spilchen
Copy link
Collaborator Author

Service packs are typically small bug fixes for the Vertica server. The next server release that we are planning for next month is a service pack update (11.1.1). More details on supported upgrade paths in Vertica:
https://www.vertica.com/docs/11.1.x/HTML/Content/Authoring/InstallationGuide/Upgrade/UpgradePaths.htm

@spilchen spilchen merged commit 10d282d into vertica:main Mar 16, 2022
@spilchen spilchen deleted the fix-upgrade-path branch March 16, 2022 00:28
spilchen pushed a commit to spilchen/vertica-kubernetes that referenced this pull request Mar 21, 2022
The upgrade path detection that was added in v1.3.0 of the operator was too
strict when it came to checking for service packs. As per the Vertica docs,
those can be skipped when doing upgrades. This PR fixes that bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants