Ad-hoc Hive Image with Red Hat Package Updates at Old Commit #2893
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
bennerv
requested review from
jewzaam,
hawkowl,
rogbas,
petrkotas,
jharrington22,
cblecker,
facchettos,
cadenmarchese,
UlrichSchlueter,
s-amann,
SudoBrendan and
ellis-johnson
as code owners
s-amann
approved these changes
May 4, 2023
cadenmarchese
approved these changes
May 4, 2023
|
Status are showing as running, but they're green in ADO. Going to force merge |
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 this PR does / why we need it:
There's an issue in hive in production where there appears to be memory leaks. We also have to take into account older versions of hive have vulnerabilities.
This hive image is a hotfix image rebuilt at the commit we were using which was good, but should have red hat update packages so no P0s 👍
Test plan for issue:
Test in INT + roll to prod.
Is there any documentation that needs to be updated for this PR?
Nope