HDDS-3859. Add ldb to ozone-runner docker image #15
Conversation
This file contains hidden or 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
elek
approved these changes
Jun 25, 2020
Member
elek
left a comment
elek
left a comment
There was a problem hiding this comment.
+1. Tested locally with docker build and worked well.
Member
|
Added git tag |
Contributor
Author
|
Thanks @elek for reviewing and committing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Add
ldband its dependencies to theozone-runnerdocker image. It is necessary for performing workaround steps (HDDS-3499) during 0.5.0 to 0.6.0 upgrade, so we need it for upgrade testing.https://issues.apache.org/jira/browse/HDDS-3859
How was this patch tested?
Built new
ozone-runnerimage locally. Started cluster with Ozone 0.5.0, created some data. Stopped the cluster, executed workaround steps in container with the new image. Restarted the cluster with currentmaster, and verified that data can be read. (Script for these steps will be provided in HDDS-3855.)ldbran fine: