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.
Description of problem:
Satellite upgrade for some customers fails with:
"[ERROR 2016-07-29 14:30:14 verbose] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<FQDN>]: Could not evaluate: Proxy <FQDN> cannot be registered (Connection refused - connect(2)): N/A"
Version-Release number of selected component (if applicable):
Satellite 6.1.9 upgrade attempt to 6.2.0
How reproducible:
I have reproduced this on my own private instance. Other customers have as well.
Steps to Reproduce:
1. https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server
While running the command at step 17 " satellite-installer --scenario satellite --upgrade --verbose --noop"
2.hit issue
3.check installer log and find the a proxy error.
4. Seems to be the same issue as noted in this foreman bug with httpd not running:
projects.theforeman.org/issues/3083
Actual results:
upgrade fails
Expected results:
upgrade should succeed
Additional info:
Hello
is this not really a docs bug?
Please see new text at link [1]
We changed the text a bit and used bold to emphasize that this was an optional step. We also added a substep to add an include line in '/etc/httpd/conf/httpd.conf' for '/etc/httpd/conf.modules.d/*.conf' to stop the error occurring that was confusing people.
This is the fist two lines from the step (currently step 18) at [1]
QUOTE: If you have custom configurations, they will be reverted to the installation defaults in the next step. If you want to see what will be changed *when you perform the upgrade*,
near the end is this line:
QUOTE: to see what changes *would be applied* if the --noop option was omitted
[1]
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server#upgrading_satellite_server