pinning UBI to 8.0 and don't update packages #273
Merged
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
hendolim
requested review from
arctan5x,
bb03,
jmeixensperger,
jonathan-vega-splunk,
jrigassio-splunk,
lephino,
mikedickey and
nwang92
bb03
approved these changes
Nov 7, 2019
arctan5x
approved these changes
Nov 7, 2019
jrigassio-splunk
approved these changes
Nov 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
splunk/splunk:edge is currently broken because Redhat pushed UBI 8.1 as the latest UBI which contains update to libdnf that breaks microdnf.
This PR pins the UBI to 8.0 and remove update to prevent that from happenning.
I will monitor updates from them and change this back to pull from latest once they publish the fix.
Created this ticket to keep track https://jira.splunk.com/browse/CSPL-173