Execution
Date
08 May 2024 15:01:00 +0100
Duration
00:05:54.52
Controller
ssh-gw-4.layershift.com
User
root
Versions
Ansible
2.16.4
ara
1.7.1 / 1.7.2.dev2
Python
3.10.10
Summary
478
Hosts
1
Tasks
478
Results
1
Plays
1
Files
0
Records
Task result details
-
StatusFAILED
-
Duration00:04:06.91
-
PlayAnsible Ad-Hoc
-
Taskshell
-
Date08 May 2024 15:05:50 +0100
-
Module / Actionshell (Ad-Hoc: shell: yum -y install jq:1)
| Field | Value |
|---|---|
| changed |
True |
| cmd |
yum -y install jq |
| delta |
0:00:01.169525 |
| end |
2024-05-08 15:01:46.170232 |
| invocation |
{ "module_args": { "_raw_params": "yum -y install jq", "_uses_shell": true, "argv": null, "chdir": null, "creates": null, "executable": null, "expand_argument_vars": true, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true } } |
| msg |
non-zero return code |
| rc |
1 |
| start |
2024-05-08 15:01:45.000707 |
| stderr |
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
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
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:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
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:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
|
| stderr_lines |
[ "", "", " 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", " distribution release than is supported by the repository (and the", " packages for the previous distribution release still work).", "", " 3. Run the command with the repository temporarily disabled", " yum --disablerepo=<repoid> ...", "", " 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:", "", " yum-config-manager --disable <repoid>", " or", " subscription-manager repos --disable=<repoid>", "", " 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:", "", " yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true", "", "Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again" ] |
| stdout |
Loaded plugins: fastestmirror, tsflags Determining fastest mirrors |
| stdout_lines |
[ "Loaded plugins: fastestmirror, tsflags", "Determining fastest mirrors" ] |