Bug 1365542
Summary: | Upgrades fail if a proxy is set on the system | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | David Davis <daviddavis> |
Component: | Installation | Assignee: | David Davis <daviddavis> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.0 | CC: | bbuckingham, chrobert, jcallaha, ktordeur, mmccune, nshaik, pmoravec, xdmoon, zhunting |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | katello-3.0.0-11 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-22 06:36:18 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
David Davis
2016-08-09 13:47:40 UTC
Created redmine issue http://projects.theforeman.org/issues/16028 from this bug For user scenario "http_proxy env. variable set, running installer / upgrade fails", the fix above isn't sufficient. Installer then raises an error during foreman-rake db:seed: [DEBUG 2016-08-09 15:46:49 main] Executing '/usr/sbin/foreman-rake db:seed' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: rake aborted! [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Net::HTTPServerException: 407 "Proxy Authentication Required" [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.37/lib/restclient_ext/request.rb:44:in `transmit' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:51:in `get' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.0/lib/runcible/base.rb:78:in `get_response' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.0/lib/runcible/base.rb:66:in `call' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.0/lib/runcible/resources/event_notifier.rb:48:in `list' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.68/app/models/katello/glue/pulp/repo.rb:32:in `ensure_sync_notification' [ WARN 2016-08-09 15:47:19 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.68/db/seeds.d/108-ensure_sync_notification.rb:9:in `<top (required)>' .. The cause is, 108-ensure_sync_notification.rb makes a ruby restclient call to pulp: client=https://satellite.example.com, path=/pulp/api/v2/events/, args=[:get, {"content_type"=>"application/json", "accept"=>"application/json"}] that fails. No idea ATM why, if it makes the call against FQDN of Satellite with no proxy set (RestClient.proxy isnt apparently set, I expect). Consequence: activation keys disappear in WebUI (huh? why? but this has been seen at 2 customers already). Not sure if it is worth filing extra BZ or to fix this flaw under the same one since same basic user story is failing. Pavel, it's probably going to require a separate fix. Moreover, I tried to reproduce the error by setting $http_proxy and $https_proxy and running foreman-rake db:seed but couldn't. I'll need to dig into it some more. Moving to POST since upstream bug http://projects.theforeman.org/issues/16028 has been closed (In reply to David Davis from comment #5) > Pavel, it's probably going to require a separate fix. Moreover, I tried to > reproduce the error by setting $http_proxy and $https_proxy and running > foreman-rake db:seed but couldn't. I'll need to dig into it some more. Raised as https://bugzilla.redhat.com/show_bug.cgi?id=1366139 Verified in Satellite 6.2.1 Snap 1.3. Upgrade from Satellite 6.1.8 executed without issue. Proxy variables were set before upgrade and remained after, but did not affect the upgrade itself. [root@rhsm-qe-1 ~]# echo $http_proxy 120.26.142.73 [root@rhsm-qe-1 ~]# echo $https_proxy 120.26.142.73 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:1643 |