Description of problem: Capsule upgrade fails with Proxy <fqdn> cannot be registered (Could not load data from https://<fqdn>) Version-Release number of selected component (if applicable): 6.2.0-Snap14.1 How reproducible: 1/1 Steps to Reproduce: 0. @SAT run capsule-certs-generate and copy tar to a capsule 1. workaround #1341712: re-register the 6.1.9 capsule with upgraded 6.2 satellite, resume failed registration task 2. setup capsule 6.2 repo 3. yum update -y 4. run installer and apply workaround #1342449 (use pulp-oauth-secret during upgade) # satellite-installer -S capsule --upgrade --certs-tar $(hostname).tar --pulp-oauth-secret 2XbJviPGaW4wTZVv2Ln49iwtenkQKzT5 Upgrading... Upgrade Step: stop_services... Upgrade Step: start_databases... Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... Upgrade Step: fix_pulp_httpd_conf... Upgrade Step: start_httpd... Upgrade Step: start_qpidd... Upgrade Step: start_pulp... Upgrade Step: remove_nodes_importers... Upgrade Step: Running installer... Installing +++ /tmp/puppet-file20160605-15322-1sx88ce-003-cr2016- [77%] [............................ /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Could not evaluate: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Failed to call refresh: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> Installing Done [100%] [....................................] Something went wrong! Check the log for ERROR-level output The full log is at /var/log/foreman-installer/capsule.log Upgrade Step: restart_services... /var/log/foreman-installer/capsule.log: [ WARN 2016-06-05 11:38:21 main] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: ensure changed 'stopped' to 'running' [ INFO 2016-06-05 11:38:21 main] RESOURCE Service[foreman-proxy] [DEBUG 2016-06-05 11:38:21 main] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: The container Class[Foreman_proxy::Service] will propagate my refresh event [ INFO 2016-06-05 11:38:21 main] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Unscheduling refresh on Service[foreman-proxy] [DEBUG 2016-06-05 11:38:21 main] Class[Foreman_proxy::Service]: The container Stage[main] will propagate my refresh event [ INFO 2016-06-05 11:38:21 main] Class[Foreman_proxy::Service]: Scheduling refresh of Class[Foreman_proxy::Register] [ INFO 2016-06-05 11:38:21 main] Class[Foreman_proxy::Register]: Scheduling refresh of Foreman_smartproxy[<CAPSULE_FQDN>] [DEBUG 2016-06-05 11:38:21 main] Class[Foreman_proxy::Plugin::Pulp]: The container Stage[main] will propagate my refresh event [ERROR 2016-06-05 11:38:22 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Could not evaluate: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> [ INFO 2016-06-05 11:38:22 main] - is your server down? [ INFO 2016-06-05 11:38:22 main] - was rake apipie:cache run when using apipie cache? (typical production settings)): N/A [ INFO 2016-06-05 11:38:22 main] /usr/lib/ruby/site_ruby/1.8/puppet/util/errors.rb:106:in `fail' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:7:in `raise_error' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:59:in `proxy' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:63:in `id' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:67:in `exists?' [ INFO 2016-06-05 11:38:22 main] /usr/lib/ruby/site_ruby/1.8/puppet/property/ensure.rb:81:in `retrieve' [ INFO 2016-06-05 11:38:22 main] /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1048:in `retrieve' ... [ INFO 2016-06-05 11:38:22 main] RESOURCE Foreman_smartproxy[<CAPSULE_FQDN>] [ERROR 2016-06-05 11:38:22 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Failed to call refresh: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> [ INFO 2016-06-05 11:38:22 main] - is your server down? [ INFO 2016-06-05 11:38:22 main] - was rake apipie:cache run when using apipie cache? (typical production settings)): N/A [ERROR 2016-06-05 11:38:22 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Proxy <CAPSULE_FQDN> cannot be registered (Could not load data from https://<CAPSULE_FQDN> [ INFO 2016-06-05 11:38:22 main] - is your server down? [ INFO 2016-06-05 11:38:22 main] - was rake apipie:cache run when using apipie cache? (typical production settings)): N/A [ INFO 2016-06-05 11:38:22 main] /usr/lib/ruby/site_ruby/1.8/puppet/util/errors.rb:106:in `fail' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:7:in `raise_error' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:101:in `refresh_features!' [ INFO 2016-06-05 11:38:22 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/type/foreman_smartproxy.rb:49:in `refresh' [ INFO 2016-06-05 11:38:22 main] /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:101:in `send' ... Actual results: error during capsule upgrade Expected results: no error during capsule upgrade
Not sure if the error is induced by using workaround for #1341712 (6.1.9 capsule re-registration within the upgraded 6.2 satellite and failed registration task resuming)
Capsule is on RHEL6
By adding --register-in-foreman false option you avoid to hit this issue
The changes coming with bug 1341756 will address this; however, rather than close this as a duplicate, I'd like it to go through verification to ensure it is fixed.
VERIFIED. @satellite-capsule-6.2.0-17.0.el6sat.noarch katello-installer-base-3.0.0.46-1.el6sat.noarch foreman-installer-katello-3.0.0.46-1.el6sat.noarch Upgrade 6.1.9 -> 6.2.0 Snap17: 1. # satellite-installer --upgrade --certs-tar $(hostname).tar Upgrading... Upgrade Step: stop_services... Upgrade Step: start_databases... Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... Upgrade Step: fix_pulp_httpd_conf... Upgrade Step: start_httpd... Upgrade Step: start_qpidd... Upgrade Step: start_pulp... Upgrade Step: remove_nodes_importers... Upgrade Step: Running installer... Installing Done [100%] [....................................] The full log is at /var/log/foreman-installer/capsule.log Upgrade Step: restart_services... Katello upgrade completed! 2. # grep -A3 trusted_hosts: /etc/foreman-proxy/settings.yml :trusted_hosts: - <SAT_FQDN> - <CAPSULE_FQDN 3. # grep foreman_url: /etc/foreman-proxy/settings.yml :foreman_url: https://<SAT_FQDN>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501