Skip to content

yum flake network unreachable #16103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
tbielawa opened this issue Sep 1, 2017 · 5 comments
Closed

yum flake network unreachable #16103

tbielawa opened this issue Sep 1, 2017 · 5 comments
Assignees
@sdodson @jupierce
Labels
component/internal-tools kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2

Comments

@tbielawa
Copy link
Contributor

tbielawa commented Sep 1, 2017 

[openshift/origin-logging-kibana] --> RUN rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch &&     INSTALLED_PKGS="kibana-${KIBANA_VER}" &&     yum install -y --setopt=tsflags=nodocs  ${INSTALLED_PKGS} &&     yum clean all
[openshift/origin-logging-kibana] Loaded plugins: fastestmirror, ovl
[openshift/origin-logging-kibana] http://centos.sonn.com/7.3.1611/updates/x86_64/repodata/33fdce604445f67a26ce5ddc354ea0c835ed119ac8cb7404cc2b565bf80722a1-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2001:470:113:3:20c:29ff:fe57:4fcc: Network is unreachable"

Observed in:
@tbielawa tbielawa added the kind/test-flake Categorizes issue or PR as related to test flakes. label Sep 1, 2017
@tbielawa tbielawa mentioned this issue Sep 1, 2017
Merged
@jupierce
Copy link
Contributor

jupierce commented Sep 1, 2017

I think @sdodson has a plan to wrap yum interactions with retries.

@tbielawa
Copy link
Contributor Author

tbielawa commented Sep 1, 2017

Yep. We're working on that in our arch meetings and in openshift/openshift-ansible#5125

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 19, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 21, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdodson sdodson

@jupierce jupierce

Labels
component/internal-tools kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@tbielawa @sdodson @openshift-bot @pweil- @jupierce @openshift-ci-robot