Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1379458

Summary: Can't update from 6.3.0 Snap 1 to snap3
Product: Red Hat Satellite Reporter: Perry Gagne <pgagne>
Component: InstallationAssignee: Eric Helms <ehelms>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bkearney, ehelms
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-08 21:12:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Perry Gagne 2016-09-26 19:40:07 UTC 
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.
Comment 1 Perry Gagne 2016-09-28 15:09:31 UTC 
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"