Cleaning yum

clean.log

[root@viaq openshift-ansible]# yum clean all
Loaded plugins: fastestmirror, langpacks
Repository centos-openshift-origin is listed more than once in the configuration
Cleaning repos: base centos-openshift-origin centos-openshift-origin14-candidate centos-openshift-origin15-candidate docker-ce-edge docker-ce-stable epel extras updates
Cleaning up everything
[root@viaq openshift-ansible]# yum repolist 
Loaded plugins: fastestmirror, langpacks
Repository centos-openshift-origin is listed more than once in the configuration
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirror.centos.org; Unknown error"
Trying other mirror.
http://cbs.centos.org/repos/paas7-openshift-origin14-candidate/x86_64/os/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: cbs.centos.org; Unknown error"
Trying other mirror.
http://cbs.centos.org/repos/paas7-openshift-origin15-candidate/x86_64/os/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: cbs.centos.org; Unknown error"
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/edge/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: download.docker.com; Unknown error"
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: download.docker.com; Unknown error"
Trying other mirror.
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"


 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
[root@viaq openshift-ansible]#