[yum] Clear cached data and add retry loop #19182
Merged
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
This commit makes the yum commands more robust by: - clearing the cache after the install command is finished - adding a retry loop so that the installation is retried in case of transient network issues Without this fix, the Unified Release Process can't complete any Stack/Solution snapshots or staging builds because of the following error: ``` "[Errno -1] repomd.xml does not match metalink for epel" ``` This is related to this [Slack discussion for building the 7.8.0 BC7](https://elastic.slack.com/archives/C0JFN9HJL/p1592055371477200) and related to this https://serverfault.com/questions/1021273/yum-install-jq-is-failing-intermittently-on-centos7 This is inspired by what the Elasticsearch team is doing for building the Elasticsearch Docker image - https://github.com/elastic/dockerfiles/blob/a5749cb11d8b38491c40efa476c576ab60a3a9f8/elasticsearch/Dockerfile#L16
botelastic
bot
added
the
needs_team
|
This pull request doesn't have a |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
--------------------- >> end captured stdout << ----------------------
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
@mikemadden42 Thanks for the review, let me know if I can merge it even if some tests are failing |
|
@mgreau I'll go ahead & merge it. I do not believe any of our tests would exercise this change. |
|
Thank you! Let me know if I need to do the backport(PR?) for having it in 7.8 |
mgreau
added a commit
that referenced
this pull request
Jun 13, 2020
This commit makes the yum commands more robust by: - clearing the cache after the install command is finished - adding a retry loop so that the installation is retried in case of transient network issues Without this fix, the Unified Release Process can't complete any Stack/Solution snapshots or staging builds because of the following error: ``` "[Errno -1] repomd.xml does not match metalink for epel" ``` This is related to this [Slack discussion for building the 7.8.0 BC7](https://elastic.slack.com/archives/C0JFN9HJL/p1592055371477200) and related to this https://serverfault.com/questions/1021273/yum-install-jq-is-failing-intermittently-on-centos7 This is inspired by what the Elasticsearch team is doing for building the Elasticsearch Docker image - https://github.com/elastic/dockerfiles/blob/a5749cb11d8b38491c40efa476c576ab60a3a9f8/elasticsearch/Dockerfile#L16
|
@mikemadden42 I opened #19184 |
mgreau
added a commit
that referenced
this pull request
Jun 14, 2020
This commit makes the yum commands more robust by: - clearing the cache after the install command is finished - adding a retry loop so that the installation is retried in case of transient network issues Without this fix, the Unified Release Process can't complete any Stack/Solution snapshots or staging builds because of the following error: ``` "[Errno -1] repomd.xml does not match metalink for epel" ``` This is related to this [Slack discussion for building the 7.8.0 BC7](https://elastic.slack.com/archives/C0JFN9HJL/p1592055371477200) and related to this https://serverfault.com/questions/1021273/yum-install-jq-is-failing-intermittently-on-centos7 This is inspired by what the Elasticsearch team is doing for building the Elasticsearch Docker image - https://github.com/elastic/dockerfiles/blob/a5749cb11d8b38491c40efa476c576ab60a3a9f8/elasticsearch/Dockerfile#L16
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jun 15, 2020
…ngs-archive * upstream/master: Fix minor spelling error in Jenkinsfile (elastic#19153) [CI] fail if not possible to install python3 (elastic#19164) [Elastic Agent] Improved mage demo experience (elastic#18445) [yum] Clear cached data and add retry loop (elastic#19182) fix lint job by updating NOTICE (elastic#19161) Fix tags for coredns/envoyproxy (elastic#19134) Disable host.* fields by default for CrowdStrike module (elastic#19132) Allow host.* fields to be disabled in Zeek module (elastic#19113) Rename to management.Manager, add UpdateStatus to Manager interface. (elastic#19114) Edit Elastic Agent docs (elastic#19146) [JJBB] create job definition for the golang-crossbuild project (elastic#19162) Fix incorrect usage of hints builder when exposed port is a substring of the hint (elastic#19052) Add basic cloudfoundry integration tests (elastic#19018)
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
This commit makes the yum commands more robust by: - clearing the cache after the install command is finished - adding a retry loop so that the installation is retried in case of transient network issues Without this fix, the Unified Release Process can't complete any Stack/Solution snapshots or staging builds because of the following error: ``` "[Errno -1] repomd.xml does not match metalink for epel" ``` This is related to this [Slack discussion for building the 7.8.0 BC7](https://elastic.slack.com/archives/C0JFN9HJL/p1592055371477200) and related to this https://serverfault.com/questions/1021273/yum-install-jq-is-failing-intermittently-on-centos7 This is inspired by what the Elasticsearch team is doing for building the Elasticsearch Docker image - https://github.com/elastic/dockerfiles/blob/a5749cb11d8b38491c40efa476c576ab60a3a9f8/elasticsearch/Dockerfile#L16
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 does this PR do?
This commit makes the yum commands more robust by:
This is inspired by what the Elasticsearch team is doing for building the Elasticsearch Docker image
Why is it important?
Without this fix, the Unified Release Process can't complete any Stack/Solution snapshots or staging builds because of the following error:
This is related to this https://serverfault.com/questions/1021273/yum-install-jq-is-failing-intermittently-on-centos7
@andrewkroh I don't know how to test it.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.