-- Logs begin at Tue 2017-12-05 13:29:29 CET. -- Jan 24 14:49:02 dco operations-upgrade[42380]: Operations::OperationsLib::executePrivate non zero exit value(1) for command: export LANG=en_US.UTF-8; yum check-update Loaded plugins: fastestmirror Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#7 - "Failed to connect to 2607:f8f8:700:12::10: Network is unreachable" 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= ... 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 or subscription-manager repos --disable= 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=.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 Jan 24 14:49:02 dco operations-upgrade[42380]: Operations::OperationsLib::removeFile Removing file '/var/run/dco/upgrade-running' Jan 24 14:49:02 dco operations-upgrade[42380]: Operations::UpgradeManager::validatePreUpgrade 'yum check-update' *failed* Not proceeding with online update. Please address the situation or pick 'offline' as an update option. Jan 24 14:49:02 dco operations-upgrade[42380]: Platform.pm completed validate-pre-upgrade in 28.3243119716644 secs with exit value: 1. -- Logs begin at Tue 2017-12-05 13:29:29 CET. -- Jan 24 15:16:16 dco operations-upgrade[44710]: Operations::OperationsLib::executePrivate non zero exit value(1) for command: export LANG=en_US.UTF-8; yum check-update Loaded plugins: fastestmirror Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#7 - "Failed to connect to 2001:4178:5:200::10: Network is unreachable" 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= ... 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 or subscription-manager repos --disable= 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=.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 Jan 24 15:16:16 dco operations-upgrade[44710]: Operations::OperationsLib::removeFile Removing file '/var/run/dco/upgrade-running' Jan 24 15:16:16 dco operations-upgrade[44710]: Operations::UpgradeManager::validatePreUpgrade 'yum check-update' *failed* Not proceeding with online update. Please address the situation or pick 'offline' as an update option. Jan 24 15:16:16 dco operations-upgrade[44710]: Platform.pm completed validate-pre-upgrade in 28.325679063797 secs with exit value: 1.