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

Unified image code clean up and make use of the same constant #2051

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

johscheuer
Copy link
Member

Description

Fixes: #2043

Type of change

Please select one of the options below.

  • Bug fix (non-breaking change which fixes an issue)

Discussion

We changed the disk layout with the unified image, if only a single storage server per pod is used, then the data directory is still suffixed with /1. This would break the transition to the unified image for cluster with a single storage server per pod.

I also made sure we remove some internal method duplications.

Testing

Updated the unit tests and CI will run e2e tests.

Documentation

Follow-up

@johscheuer johscheuer added the bug Something isn't working label Jun 5, 2024
Copy link
Contributor

@nicmorales9 nicmorales9 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 to me! thanks for the cleanup as usual!

@foundationdb-ci
Copy link

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

  • Commit ID: 4639890
  • Duration 2:40:14
  • Result: ✅ SUCCEEDED
  • Error: N/A
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@johscheuer johscheuer merged commit d1a6b30 into FoundationDB:main Jun 6, 2024
8 checks passed
@johscheuer johscheuer deleted the unified-image-cleanup branch June 6, 2024 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

processGroupNeedsRemovalForPod flag logic can be more nicely consolidated
3 participants