fix(ci): use rpm instead of zypper to install mongosh in suse docker images #2056
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
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.
For some reason somewhere around June 26th suse tests started to fail because man page for
mongoshwas missing. I couldn't track it to the root cause or some issue I can link to, but seems like after a certain updatezypperjust stopped extracting all the files from the rpm package, like they are 100% there in the rpm, rpm can list them, but they are just not installed in those directories that are listed in rpm.Switching to use
rpmdirecty to installmongoshseems to work around this (at least locally, hopefully CI will confirm this too). I am not sure whether or not we specifically want to test thatzypperinstallsmongoshcorrectly, but maybe even if that's the case we can apply the workaround for now to unblock the CI.