Hide Forgot
Description of problem: I Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. yum update 2. satellite-install --upgrade Actual results: Failed during satellite-install --upgrade Expected results: Upgrade completes Additional info: Got this error: Upgrade Step: Running installer... /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com]: Could not evaluate: Proxy qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be retrieved: unknown error (response 500) /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com]: Failed to call refresh: Proxy qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be retrieved: unknown error (response 500) /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com]: Proxy qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be retrieved: unknown error (response 500) Installing Done [100%] [......................................................................] Something went wrong! Check the log for ERROR-level output The full log is at /var/log/foreman-installer/satellite.log Upgrade failed during the installation phase. Fix the error and re-run the upgrade.
This seems to be related to the fact that the installer shouldn't try to install passenger, which is also causing a related issues: [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ERROR 2016-09-28 17:44:39 verbose] Execution of '/usr/bin/yum -d 0 -e 0 -y list shim' returned 1: One of the configured repositories failed (passenger), [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] and yum doesn't have enough cached data to continue. At this point the only [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] safe thing yum can do is fail. There are a few ways to work "fix" this: [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] 1. Contact the upstream for the repository and get them to fix the problem. [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] 2. Reconfigure the baseurl/etc. for the repository, to point to a working [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] upstream. This is most often useful if you are using a newer [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] distribution release than is supported by the repository (and the [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] packages for the previous distribution release still work). [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] 3. Disable the repository, so yum won't use it by default. Yum will then [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] just ignore the repository until you permanently enable it again or use [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] --enablerepo for temporary usage: [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] yum-config-manager --disable passenger [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] 4. Configure the failing repository to be skipped, if it is unavailable. [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] Note that yum will try to contact the repo. when it runs most commands, [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] so will have to try and fail each time (and thus. yum will be be much [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] slower). If it is a very temporary problem though, this is often a nice [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] compromise: [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] yum-config-manager --save --setopt=passenger.skip_if_unavailable=true [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] failure: repodata/repomd.xml from passenger: [Errno 256] No more mirrors to try. [qe-sat6-feature-rhel7.satqe.lab.eng.rdu2.redhat.com] out: [ INFO 2016-09-28 17:44:39 verbose] https://oss-binaries.phusionpassenger.com/yum/passenger/el/7Server/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: oss-binaries.phusionpassenger.com; Name or service not known"