centos job failure with epel-release install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-midonet |
In Progress
|
Critical
|
YAMAMOTO Takashi |
Bug Description
ipv6 reachability issue?
2604:1580:
+ functions-
+ functions-
++ functions-
+ functions-
+ functions-
+ functions-
Loaded plugins: fastestmirror
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
or
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
Cannot find a valid baseurl for repo: epel-bootstrap/
Could not retrieve mirrorlist http://
14: curl#7 - "Failed to connect to 2605:bc80:
+ functions-
YUM_FAILED 1
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
++ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ functions-
+ ./stack.
+ functions-
+ functions-
[Call Trace]
./stack.
./stack.sh:324:die
[ERROR] ./stack.sh:324 Error installing EPEL repo, cannot continue
Changed in networking-midonet: | |
assignee: | nobody → YAMAMOTO Takashi (yamamoto) |
importance: | Undecided → Critical |
milestone: | none → 6.0.0 |
status: | New → In Progress |
tags: | added: gate-failure midokura-jira-tracked |
description: | updated |
Changed in networking-midonet: | |
milestone: | 6.0.0 → 7.0.0 |
Changed in networking-midonet: | |
milestone: | 7.0.0 → 8.0.0 |
there seems to be no obvious correlation with node_provider etc.
project: "openstack/ networking- midonet" AND build_node: "centos- 7" AND message:"At completion, logs for this job will be available at"