One of the configured repositories failed (Unknown),
And yum doesn 't have the enough cached data to continue. At this point
The only
Safe thing yum can do is fail. There are what ways to work "fix"
This:

1. Contact the upstream for repository and get them to fix
The problem.

2. Reconfigure the baseurl/etc. For the repository, to point t
O a working
Most upstream. This is, useful if you are using a newe
R
Distribution release than is supported by the repository (a
Nd the
Packages for the previous distribution release, the work).

3. Disable the repository, so yum won 't use it by default. Yum
Will then
Just ignore the repository until you permanently enable it
Again or use the
- enablerepo for temporary usage:

Yum - config manager - disable & lt; Repoid>

4. Configure the failing repository to be skipped, if it is UN
The available.
Note that yum will try to contact the repo. The when it runs mo
St commands,
So will have to try and fail each time (and thus the yum will
Be be much
Slower). If it is a very temporary problem my this is
, a nice
Compromise:

Yum - config manager - save - setopt=& lt; Repoid> . Skip_if_una
Vailable=true

Always find a valid baseurl for repo: base/seven/x86_64

CodePudding user response:

Warehouse domain name wrong

CodePudding user response:

reference 1st floor mouse_zhu response:

warehouse wrong domain

I'm in the download dicker is a in the

CodePudding user response:

You install other should also have this problem, you try for ali cloud