HDDS-11810. Secure acceptance test on arm64 fails with LoginException: Checksum failed #7498
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…: Checksum failed
ChenSammi
approved these changes
Nov 28, 2024
|
Thanks @ChenSammi for reporting this and for the review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Kerberos-enabled acceptance tests in Ozone use the
ozone-testkrb5Docker image as KDC. Keytab files are exported from the KDC at development time, runningupdate-keytabs.sh, then added to Git. Ozone services access these via volume mounted in each container.Multi-arch Docker images present a problem: keytab generation uses a specific platform variant of the image (depending on the architecture of the computer
update-keytabs.shis run on). Keytabs work only with that variant. Therefore Keytabs pre-generated with the amd64 image do not work with arm64 one:This PR proposes to defer keytab export to the time when tests start the Docker Compose cluster. This ensures both use the same variant of the
ozone-testkrb5image. Pre-generated keytabs are no longer needed, removed from the repo.https://issues.apache.org/jira/browse/HDDS-11810
How was this patch tested?
Tested on amd64 locally and in CI:
https://github.com/adoroszlai/ozone/actions/runs/12058615470
@ChenSammi tested it on arm64.