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 1561750 - [Satellite 6.3] Smart proxy register error while upgrading Satellite from 6.2.14 to 6.3
Summary: [Satellite 6.3] Smart proxy register error while upgrading Satellite from 6.2...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: Unspecified
Assignee: Ewoud Kohl van Wijngaarden
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-28 19:49 UTC by Varatharaja Perumal G
Modified: 2022-03-13 14:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-24 13:21:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23054 0 Normal Closed Smart proxy register error when apache is not started first 2021-01-28 19:29:51 UTC
Red Hat Knowledge Base (Solution) 3425081 0 None None None 2018-05-10 17:16:18 UTC

Description Varatharaja Perumal G 2018-03-28 19:49:55 UTC
Description of problem:

Smart proxy register error while upgrading Satellite from 6.2.14 to 6.3

~~~
 INFO 2018-03-27 14:52:48 main] Puppet has finished, bye!
[ INFO 2018-03-27 14:52:48 main] Executing hooks in group post
[DEBUG 2018-03-27 14:52:48 main] Hook /usr/share/katello-installer-base/hooks/post/10-post_install.rb returned nil
[ INFO 2018-03-27 14:52:48 main] pulp.conf is already present, skipping
[DEBUG 2018-03-27 14:52:48 main] Hook /usr/share/katello-installer-base/hooks/post/29-create_package_httpd_conf.rb returned ["pulp.conf"]
[ERROR 2018-03-27 14:52:48 main] Upgrade failed during the installation phase. Fix the error and re-run the upgrade.
[DEBUG 2018-03-27 14:52:48 main] Hook /usr/share/katello-installer-base/hooks/post/30-upgrade.rb returned [<Logging::Logger:0xdb22e8 name="main">, <Logging::Logger:0xdbdae4 n
ame="fatal">]
[DEBUG 2018-03-27 14:52:48 main] Hook /usr/share/katello-installer-base/hooks/post/31-upgrade-puppet.rb returned nil
[ INFO 2018-03-27 14:52:48 main] All hooks in group post finished
[DEBUG 2018-03-27 14:52:48 main] Exit with status code: 6 (signal was 6)
[ERROR 2018-03-27 14:52:48 main] Errors encountered during run:
[ERROR 2018-03-27 14:52:48 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite.example.com]: Could not evaluate: Exception Connection refused - co
nnect(2) in get request to: https://satellite.example.com/api/v2/smart_proxies?search=name=%22satellite.example.com%22
~~~
Version-Release number of selected component (if applicable):

Satellite 6.3

Actual results:

Smart proxy registration fails

[ERROR 2018-03-27 14:52:48 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite.example.com]: Could not evaluate: Exception Connection refused - co
nnect(2) in get request to: https://satellite.example.com/api/v2/smart_proxies?search=name=%22satellite.example.com%22

Expected results:

The upgrade should complete successfully.

Additional info:

Workaround suggested by Stephen.

~~~
1) Backup the file 

# cp  /usr/share/foreman-installer/modules/foreman_proxy/manifests/register.pp  /usr/share/foreman-installer/modules/foreman_proxy/manifests/register.pp.bk

2) Add httpd service as required.

***
# Register the foreman proxy
class foreman_proxy::register {

  if $foreman_proxy::register_in_foreman {
    foreman_smartproxy { $foreman_proxy::registered_name:
      ensure          => present,
      base_url        => $foreman_proxy::foreman_base_url,
      consumer_key    => $foreman_proxy::oauth_consumer_key,
      consumer_secret => $foreman_proxy::oauth_consumer_secret,
      effective_user  => $foreman_proxy::oauth_effective_user,
      ssl_ca          => pick($foreman_proxy::foreman_ssl_ca, $foreman_proxy::ssl_ca),
      url             => $foreman_proxy::real_registered_proxy_url,
      require         => Service['httpd'],
    }
  }

}

***

~~~

Comment 1 Stephen Benjamin 2018-03-28 22:23:50 UTC
Created redmine issue http://projects.theforeman.org/issues/23054 from this bug

Comment 3 Satellite Program 2018-12-06 21:05:05 UTC
Upstream bug assigned to ekohlvan

Comment 4 Satellite Program 2018-12-06 21:05:09 UTC
Upstream bug assigned to ekohlvan

Comment 5 Satellite Program 2018-12-17 01:04:34 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23054 has been resolved.


Note You need to log in before you can comment on or make changes to this bug.