-- Logs begin at Thu 2018-02-15 10:29:59 MSK. --
Apr 20 14:25:20 dco operations-upgrade[6211]: done
Apr 20 14:25:20 dco operations-upgrade[6212]: Listing yum repositories...
Apr 20 14:25:48 dco operations-upgrade[6220]: done
Apr 20 14:25:48 dco operations-upgrade[6221]: Cleaning yum cache: yum clean all
Apr 20 14:25:48 dco operations-upgrade[6224]: Loaded plugins: fastestmirror
Apr 20 14:25:48 dco operations-upgrade[6225]: Cleaning repos: base centos-specific-swdco-local-rpms extras swdco-local-rpms
Apr 20 14:25:48 dco operations-upgrade[6226]: : thirdparty-swdco-local-rpms updates
Apr 20 14:25:48 dco operations-upgrade[6227]: Cleaning up everything
Apr 20 14:25:48 dco operations-upgrade[6228]: Just checking if we have updates wating: yum check-update  -y
Apr 20 14:25:48 dco operations-upgrade[6231]: Loaded plugins: fastestmirror
Apr 20 14:26:16 dco operations-upgrade[6256]: One of the configured repositories failed (Unknown),
Apr 20 14:26:16 dco operations-upgrade[6257]: and yum doesn't have enough cached data to continue. At this point the only
Apr 20 14:26:16 dco operations-upgrade[6258]: safe thing yum can do is fail. There are a few ways to work "fix" this:
Apr 20 14:26:16 dco operations-upgrade[6260]: 1. Contact the upstream for the repository and get them to fix the problem.
Apr 20 14:26:16 dco operations-upgrade[6262]: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
Apr 20 14:26:16 dco operations-upgrade[6263]: upstream. This is most often useful if you are using a newer
Apr 20 14:26:16 dco operations-upgrade[6264]: distribution release than is supported by the repository (and the
Apr 20 14:26:16 dco operations-upgrade[6265]: packages for the previous distribution release still work).
Apr 20 14:26:16 dco operations-upgrade[6267]: 3. Run the command with the repository temporarily disabled
Apr 20 14:26:16 dco operations-upgrade[6268]: yum --disablerepo=<repoid> ...
Apr 20 14:26:16 dco operations-upgrade[6270]: 4. Disable the repository permanently, so yum won't use it by default. Yum
Apr 20 14:26:16 dco operations-upgrade[6271]: will then just ignore the repository until you permanently enable it
Apr 20 14:26:16 dco operations-upgrade[6272]: again or use --enablerepo for temporary usage:
Apr 20 14:26:16 dco operations-upgrade[6274]: yum-config-manager --disable <repoid>
Apr 20 14:26:16 dco operations-upgrade[6275]: or
Apr 20 14:26:16 dco operations-upgrade[6276]: subscription-manager repos --disable=<repoid>
Apr 20 14:26:16 dco operations-upgrade[6278]: 5. Configure the failing repository to be skipped, if it is unavailable.
Apr 20 14:26:16 dco operations-upgrade[6279]: Note that yum will try to contact the repo. when it runs most commands,
Apr 20 14:26:16 dco operations-upgrade[6280]: so will have to try and fail each time (and thus. yum will be be much
Apr 20 14:26:16 dco operations-upgrade[6281]: slower). If it is a very temporary problem though, this is often a nice
Apr 20 14:26:16 dco operations-upgrade[6282]: compromise:
Apr 20 14:26:16 dco operations-upgrade[6284]: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Apr 20 14:26:16 dco operations-upgrade[6286]: Cannot find a valid baseurl for repo: base/7/x86_64
Apr 20 14:26:16 dco operations-upgrade[6287]: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
Apr 20 14:26:16 dco operations-upgrade[6288]: 14: curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
Apr 20 14:26:16 dco operations-upgrade[6289]: Removing update repositories
Apr 20 14:26:16 dco operations-upgrade[6290]: Removing DCO yum repository...
Apr 20 14:26:16 dco operations-upgrade[6291]: done
Apr 20 14:26:16 dco operations-upgrade[6293]: Removing third party centos specific yum repository...
Apr 20 14:26:16 dco operations-upgrade[6295]: done
Apr 20 14:26:16 dco operations-upgrade[6296]: Removing third party yum repository...
Apr 20 14:26:16 dco operations-upgrade[6298]: done
Apr 20 14:26:16 dco operations-upgrade[6299]: Done
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::UpgradeManager::executeUpgradeScriptDryRun No updates to the system.
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::UpgradeManager::runUpgradeLocal Determined that updates *are* available, proceeding with system upgrade.
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::UpgradeManager::runUpgradeLocal Current DCO version is: 8.1.0-70629
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::UpgradeManager::shutdownServices Shutting down services...
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::OsManager::stopService Stopping service: operations-monitor
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::OsManager::sendCommandToService Sending command: 'stop' to service: 'operations-monitor' on host: '127.0.0.1'
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::OsManager::sendCommandToService Sending command: 'kill' to service: 'operations' on host: '127.0.0.1'
Apr 20 14:26:16 dco operations-upgrade[6185]: Operations::OsManager::sendCommandToService Sending command: 'stop' to service: 'operations' on host: '127.0.0.1'
Apr 20 14:26:17 dco operations-upgrade[6185]: Operations::OsManager::stopService Stopping service: httpd
Apr 20 14:26:17 dco operations-upgrade[6185]: Operations::OsManager::sendCommandToService Sending command: 'stop' to service: 'httpd' on host: '127.0.0.1'
Apr 20 14:26:17 dco operations-upgrade[6185]: Operations::OsManager::sendCommandToService Sending command: 'stop' to service: 'postgresql-9.5' on host: '127.0.0.1'
Apr 20 14:26:17 dco operations-upgrade[6185]: Operations::UpgradeManager::executeUpgradeScript Executing upgrade command (/bin/bash /data/upgrade/dco-install/upgrade.sh )
Apr 20 14:26:17 dco operations-upgrade[6565]: Adding third party centos specific yum repository...
Apr 20 14:26:17 dco operations-upgrade[6567]: done
Apr 20 14:26:17 dco operations-upgrade[6568]: Adding third party yum repository...
Apr 20 14:26:17 dco operations-upgrade[6570]: done
Apr 20 14:26:17 dco operations-upgrade[6571]: Adding DCO yum repository...
Apr 20 14:26:17 dco operations-upgrade[6573]: done
Apr 20 14:26:17 dco operations-upgrade[6574]: Install GPG key...
Apr 20 14:26:17 dco operations-upgrade[6576]: done
Apr 20 14:26:17 dco operations-upgrade[6577]: Listing yum repositories...
Apr 20 14:26:46 dco operations-upgrade[6580]: done
Apr 20 14:26:46 dco operations-upgrade[6581]: Cleaning yum cache: yum clean all
Apr 20 14:26:46 dco operations-upgrade[6584]: Loaded plugins: fastestmirror
Apr 20 14:26:46 dco operations-upgrade[6585]: Cleaning repos: base centos-specific-swdco-local-rpms extras swdco-local-rpms
Apr 20 14:26:46 dco operations-upgrade[6586]: : thirdparty-swdco-local-rpms updates
Apr 20 14:26:46 dco operations-upgrade[6587]: Cleaning up everything
Apr 20 14:26:46 dco operations-upgrade[6588]: Updating packages running: yum update  -y
Apr 20 14:26:46 dco operations-upgrade[6591]: Loaded plugins: fastestmirror
Apr 20 14:27:14 dco operations-upgrade[6664]: One of the configured repositories failed (Unknown),
Apr 20 14:27:14 dco operations-upgrade[6665]: and yum doesn't have enough cached data to continue. At this point the only
Apr 20 14:27:14 dco operations-upgrade[6666]: safe thing yum can do is fail. There are a few ways to work "fix" this:
Apr 20 14:27:14 dco operations-upgrade[6668]: 1. Contact the upstream for the repository and get them to fix the problem.
Apr 20 14:27:14 dco operations-upgrade[6670]: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
Apr 20 14:27:14 dco operations-upgrade[6671]: upstream. This is most often useful if you are using a newer
Apr 20 14:27:14 dco operations-upgrade[6672]: distribution release than is supported by the repository (and the
Apr 20 14:27:14 dco operations-upgrade[6673]: packages for the previous distribution release still work).
Apr 20 14:27:14 dco operations-upgrade[6675]: 3. Run the command with the repository temporarily disabled
Apr 20 14:27:14 dco operations-upgrade[6676]: yum --disablerepo=<repoid> ...
Apr 20 14:27:14 dco operations-upgrade[6678]: 4. Disable the repository permanently, so yum won't use it by default. Yum
Apr 20 14:27:14 dco operations-upgrade[6679]: will then just ignore the repository until you permanently enable it
Apr 20 14:27:14 dco operations-upgrade[6680]: again or use --enablerepo for temporary usage:
Apr 20 14:27:14 dco operations-upgrade[6682]: yum-config-manager --disable <repoid>
Apr 20 14:27:14 dco operations-upgrade[6683]: or
Apr 20 14:27:14 dco operations-upgrade[6684]: subscription-manager repos --disable=<repoid>
Apr 20 14:27:14 dco operations-upgrade[6686]: 5. Configure the failing repository to be skipped, if it is unavailable.
Apr 20 14:27:14 dco operations-upgrade[6687]: Note that yum will try to contact the repo. when it runs most commands,
Apr 20 14:27:14 dco operations-upgrade[6688]: so will have to try and fail each time (and thus. yum will be be much
Apr 20 14:27:14 dco operations-upgrade[6689]: slower). If it is a very temporary problem though, this is often a nice
Apr 20 14:27:14 dco operations-upgrade[6690]: compromise:
Apr 20 14:27:14 dco operations-upgrade[6692]: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Apr 20 14:27:14 dco operations-upgrade[6694]: Cannot find a valid baseurl for repo: base/7/x86_64
Apr 20 14:27:14 dco operations-upgrade[6695]: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
Apr 20 14:27:14 dco operations-upgrade[6696]: 14: curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
Apr 20 14:27:15 dco operations-upgrade[6699]: Loaded plugins: fastestmirror
Apr 20 14:27:43 dco operations-upgrade[6703]: One of the configured repositories failed (Unknown),
Apr 20 14:27:43 dco operations-upgrade[6704]: and yum doesn't have enough cached data to continue. At this point the only
Apr 20 14:27:43 dco operations-upgrade[6705]: safe thing yum can do is fail. There are a few ways to work "fix" this:
Apr 20 14:27:43 dco operations-upgrade[6707]: 1. Contact the upstream for the repository and get them to fix the problem.
Apr 20 14:27:43 dco operations-upgrade[6709]: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
Apr 20 14:27:43 dco operations-upgrade[6710]: upstream. This is most often useful if you are using a newer
Apr 20 14:27:43 dco operations-upgrade[6711]: distribution release than is supported by the repository (and the
Apr 20 14:27:43 dco operations-upgrade[6712]: packages for the previous distribution release still work).
Apr 20 14:27:43 dco operations-upgrade[6714]: 3. Run the command with the repository temporarily disabled
Apr 20 14:27:43 dco operations-upgrade[6715]: yum --disablerepo=<repoid> ...
Apr 20 14:27:43 dco operations-upgrade[6717]: 4. Disable the repository permanently, so yum won't use it by default. Yum
Apr 20 14:27:43 dco operations-upgrade[6718]: will then just ignore the repository until you permanently enable it
Apr 20 14:27:43 dco operations-upgrade[6719]: again or use --enablerepo for temporary usage:
Apr 20 14:27:43 dco operations-upgrade[6721]: yum-config-manager --disable <repoid>
Apr 20 14:27:43 dco operations-upgrade[6722]: or
Apr 20 14:27:43 dco operations-upgrade[6723]: subscription-manager repos --disable=<repoid>
Apr 20 14:27:43 dco operations-upgrade[6725]: 5. Configure the failing repository to be skipped, if it is unavailable.
Apr 20 14:27:43 dco operations-upgrade[6726]: Note that yum will try to contact the repo. when it runs most commands,
Apr 20 14:27:43 dco operations-upgrade[6727]: so will have to try and fail each time (and thus. yum will be be much
Apr 20 14:27:43 dco operations-upgrade[6728]: slower). If it is a very temporary problem though, this is often a nice
Apr 20 14:27:43 dco operations-upgrade[6729]: compromise:
Apr 20 14:27:43 dco operations-upgrade[6731]: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Apr 20 14:27:43 dco operations-upgrade[6733]: Cannot find a valid baseurl for repo: base/7/x86_64
Apr 20 14:27:43 dco operations-upgrade[6734]: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
Apr 20 14:27:43 dco operations-upgrade[6735]: 14: curl#7 - "Failed to connect to 2001:4178:5:200::10: Network is unreachable"
Apr 20 14:27:43 dco operations-upgrade[6739]: Loaded plugins: fastestmirror
Apr 20 14:28:11 dco operations-upgrade[6764]: One of the configured repositories failed (Unknown),
Apr 20 14:28:11 dco operations-upgrade[6765]: and yum doesn't have enough cached data to continue. At this point the only
Apr 20 14:28:11 dco operations-upgrade[6766]: safe thing yum can do is fail. There are a few ways to work "fix" this:
Apr 20 14:28:11 dco operations-upgrade[6768]: 1. Contact the upstream for the repository and get them to fix the problem.
Apr 20 14:28:11 dco operations-upgrade[6770]: 2. Reconfigure the baseurl/etc. for the repository, to point to a working
Apr 20 14:28:11 dco operations-upgrade[6771]: upstream. This is most often useful if you are using a newer
Apr 20 14:28:11 dco operations-upgrade[6772]: distribution release than is supported by the repository (and the
Apr 20 14:28:11 dco operations-upgrade[6773]: packages for the previous distribution release still work).
Apr 20 14:28:11 dco operations-upgrade[6775]: 3. Run the command with the repository temporarily disabled
Apr 20 14:28:11 dco operations-upgrade[6776]: yum --disablerepo=<repoid> ...
Apr 20 14:28:11 dco operations-upgrade[6778]: 4. Disable the repository permanently, so yum won't use it by default. Yum
Apr 20 14:28:11 dco operations-upgrade[6779]: will then just ignore the repository until you permanently enable it
Apr 20 14:28:11 dco operations-upgrade[6780]: again or use --enablerepo for temporary usage:
Apr 20 14:28:11 dco operations-upgrade[6782]: yum-config-manager --disable <repoid>
Apr 20 14:28:11 dco operations-upgrade[6783]: or
Apr 20 14:28:11 dco operations-upgrade[6784]: subscription-manager repos --disable=<repoid>
Apr 20 14:28:11 dco operations-upgrade[6786]: 5. Configure the failing repository to be skipped, if it is unavailable.
Apr 20 14:28:11 dco operations-upgrade[6787]: Note that yum will try to contact the repo. when it runs most commands,
Apr 20 14:28:11 dco operations-upgrade[6788]: so will have to try and fail each time (and thus. yum will be be much
Apr 20 14:28:11 dco operations-upgrade[6789]: slower). If it is a very temporary problem though, this is often a nice
Apr 20 14:28:11 dco operations-upgrade[6790]: compromise:
Apr 20 14:28:11 dco operations-upgrade[6792]: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Apr 20 14:28:11 dco operations-upgrade[6794]: Cannot find a valid baseurl for repo: base/7/x86_64
Apr 20 14:28:11 dco operations-upgrade[6795]: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
Apr 20 14:28:11 dco operations-upgrade[6796]: 14: curl#7 - "Failed to connect to 2001:1b48:203::4:10: Network is unreachable"
Apr 20 14:28:11 dco operations-upgrade[6798]: Update succeeded, so running finalize-upgrade
Apr 20 14:28:12 dco operations-upgrade[6800]: Removing update repositories
Apr 20 14:28:12 dco operations-upgrade[6801]: Removing DCO yum repository...
Apr 20 14:28:12 dco operations-upgrade[6802]: done
Apr 20 14:28:12 dco operations-upgrade[6804]: Removing third party centos specific yum repository...
Apr 20 14:28:12 dco operations-upgrade[6806]: done
Apr 20 14:28:12 dco operations-upgrade[6807]: Removing third party yum repository...
Apr 20 14:28:12 dco operations-upgrade[6809]: done
Apr 20 14:28:12 dco operations-upgrade[6810]: Done
Apr 20 14:28:12 dco operations-upgrade[6185]: Operations::UpgradeManager::runUpgradeLocal Upgrade process went from 8.1.0-70629 -> 8.1.0-70629
Apr 20 14:28:12 dco operations-upgrade[6185]: Operations::UpgradeManager::runUpgradeLocal The upgrade process did not result in a new version of dco.
Apr 20 14:28:12 dco operations-upgrade[6185]: Operations::UpgradeManager::runUpgradeLocal The upgrade process has completed
Apr 20 14:28:12 dco operations-upgrade[6185]: Operations::UpgradeManager::umountIso Unmount ISO
Apr 20 14:28:12 dco operations-upgrade[6185]: Operations::OperationsLib::removeFile Removing file '/var/run/dco/upgrade-running'
Apr 20 14:28:12 dco operations-upgrade[6185]:  Platform.pm completed run-upgrade-local in 172.357479095459 secs with exit value: 0.
Apr 20 14:28:12 dco operations-upgrade[6176]: Operations::OperationsLib::removeFile Removing file '/var/run/dco/upgrade-running'
Apr 20 14:28:12 dco operations-upgrade[6176]: Operations::UpgradeManager::runUpgrade There were no updates to the system.
Apr 20 14:28:12 dco operations-upgrade[6176]:  Platform.pm completed run-upgrade in 174.076945066452 secs with exit value: 0.