Project

General

Profile

Bug #19746

Error while upgrading Katello Capsule 3.1 to 3.2

Added by Andrej Krüger almost 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When I try to upgrade like it is stated in the documentation for the upgrade to version 3.2 I get the following error:
  1. foreman-installer --scenario capsule --upgrade --capsule-certs-tar /root/katello/capsule-certs/<myfqdn>.tar --certs-update-all --certs-regenerate --deploy
    ERROR: Unrecognised option '--capsule-certs-tar'

See: 'foreman-installer --help'

However if I proceed like this:
  1. foreman-installer --scenario capsule --upgrade --certs-tar /root/katello/capsule-certs/<myfqdn>.tar --certs-update-all --deploy

I can go upto this point:
Upgrade Step: Running installer...
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[lx-bwetec-lmgt.tec-ad.intra.tecosim.com]: Failed to call refresh: Proxy <myfqdn> cannot be refreshed: Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([Errno::ECONNREFUSED]: Connection refused - connect(2) for "lx-bwetec-lmgt.tec-ad.intra.tecosim.com" port 9090) for proxy https://&lt;myfqdn&gt;:9090/features Please check the proxy is configured and running on the host.
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<myfqdn>]: Proxy <myfqdn> cannot be refreshed: Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([Errno::ECONNREFUSED]: Connection refused - connect(2) for "<myfqdn>" port 9090) for proxy https://&lt;myfqdn&gt;:9090/features Please check the proxy is configured and running on the host.
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:44:in `refresh_features!'
/usr/share/foreman-installer/modules/foreman/lib/puppet/type/foreman_smartproxy.rb:54:in `refresh'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:101:in `process_callback'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:20:in `block in process_events'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:93:in `block in queued_events'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:92:in `each'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:92:in `queued_events'
/usr/share/ruby/vendor_ruby/puppet/transaction/event_manager.rb:19:in `process_events'
/usr/share/ruby/vendor_ruby/puppet/transaction.rb:221:in `eval_resource'
/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'
/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 levels) in evaluate'
/usr/share/ruby/vendor_ruby/puppet/util.rb:335:in `block in thinmark'
/usr/share/ruby/benchmark.rb:296:in `realtime'
/usr/share/ruby/vendor_ruby/puppet/util.rb:334:in `thinmark'
/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in evaluate'
/usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
/usr/share/ruby/vendor_ruby/puppet/transaction.rb:138:in `evaluate'
/usr/share/gems/gems/kafo-0.9.8/modules/kafo_configure/lib/puppet/parser/functions/add_progress.rb:31:in `evaluate_with_trigger'
/usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:169:in `block in apply'
/usr/share/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination'
/usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:112:in `as_logging_destination'
/usr/share/gems/gems/kafo-0.9.8/modules/kafo_configure/lib/kafo/puppet/report_wrapper.rb:34:in `method_missing'
/usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:168:in `apply'
/usr/share/ruby/vendor_ruby/puppet/configurer.rb:120:in `block in apply_catalog'
/usr/share/ruby/vendor_ruby/puppet/util.rb:161:in `block in benchmark'
/usr/share/ruby/benchmark.rb:296:in `realtime'
/usr/share/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark'
/usr/share/ruby/vendor_ruby/puppet/configurer.rb:119:in `apply_catalog'
/usr/share/ruby/vendor_ruby/puppet/configurer.rb:227:in `run_internal'
/usr/share/ruby/vendor_ruby/puppet/configurer.rb:134:in `block in run'
/usr/share/ruby/vendor_ruby/puppet/context.rb:64:in `override'
/usr/share/ruby/vendor_ruby/puppet.rb:246:in `override'
/usr/share/ruby/vendor_ruby/puppet/configurer.rb:133:in `run'
/usr/share/ruby/vendor_ruby/puppet/application/apply.rb:302:in `apply_catalog'
/usr/share/ruby/vendor_ruby/puppet/application/apply.rb:236:in `block in main'
/usr/share/ruby/vendor_ruby/puppet/context.rb:64:in `override'
/usr/share/ruby/vendor_ruby/puppet.rb:246:in `override'
/usr/share/ruby/vendor_ruby/puppet/application/apply.rb:198:in `main'
/usr/share/ruby/vendor_ruby/puppet/application/apply.rb:159:in `run_command'
/usr/share/ruby/vendor_ruby/puppet/application.rb:381:in `block (2 levels) in run'
/usr/share/ruby/vendor_ruby/puppet/application.rb:507:in `plugin_hook'
/usr/share/ruby/vendor_ruby/puppet/application.rb:381:in `block in run'
/usr/share/ruby/vendor_ruby/puppet/util.rb:496:in `exit_on_fail'
/usr/share/ruby/vendor_ruby/puppet/application.rb:381:in `run'
/usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run'
/usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'
/usr/bin/puppet:8:in `<main>'
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 failed during the installation phase. Fix the error and re-run the upgrade.

Do you know how to fix this ?

The port seems open:
  1. nmap -p 9090 <myfqdn>

Starting Nmap 6.40 ( http://nmap.org ) at 2017-06-02 08:57 CEST
Nmap scan report for <myfqdn> (<myip>)
Host is up (-530s latency).
PORT STATE SERVICE
9090/tcp open zeus-admin

Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds

Installed Packages:
  1. rpm qa | grep 'katello\|foreman'
    katello-client-bootstrap-1.1.0-1.el7.noarch
    katello-server-ca-1.0-1.noarch
    katello-capsule-3.2.2-1.el7.noarch
    <myfqdn>-foreman-proxy-1.0-2.noarch
    katello-selinux-3.0.1-1.el7.noarch
    tfm-rubygem-foreman_remote_execution_core-1.0.2-1.fm1_13.el7.noarch
    katello-ca-consumer
    <myfqdn>-1.0-1.noarch
    foreman-installer-katello-3.2.3-1.el7.noarch
    katello-debug-3.2.2-1.el7.noarch
    foreman-release-1.13.4-1.el7.noarch
    foreman-debug-1.13.4-1.el7.noarch
    katello-service-3.2.2-1.el7.noarch
    foreman-selinux-1.13.4-1.el7.noarch
    katello-default-ca-1.0-1.noarch
    pulp-katello-1.0.2-1.el7.noarch
    python-urllib3-1.10.2-2.katello.el7.noarch
    tfm-rubygem-foreman-tasks-core-0.1.1-1.fm1_13.el7.noarch
    foreman-proxy-1.13.4-1.el7.noarch
    katello-agent-2.7.0-1.el7.noarch
    katello-certs-tools-2.4.0-1.el7.noarch
    katello-installer-base-3.2.3-1.el7.noarch
    katello-repos-3.2.0-4.el7.noarch
    katello-agent-fact-plugin-2.7.0-1.el7.noarch
    foreman-installer-1.13.4-1.el7.noarch
    <myfqdn>-foreman-proxy-client-1.0-2.noarch

History

#1 Updated by Mario Gamboa almost 5 years ago

hi there

i got the same issue and was solved if upgrade from 3.1 to 3.3 with that you not get any error at all

#2 Updated by Mario Gamboa almost 5 years ago

Also i raise a bug http://projects.theforeman.org/issues/19329 you can check the solution to make works the capsule try to add the register capsule tell to no and make all the modifications of files manually

#3 Updated by Andrej Krüger almost 5 years ago

Upgrade from 3.1 to 3.3 worked fine, thanks for your help. I got Another Capsule with (I thought) the same configuration and no problem there with the upgrade from 3.1 -> 3.2 -> 3.3

#4 Updated by Andrej Krüger almost 5 years ago

  • Status changed from New to Resolved

#5 Updated by Eric Helms almost 5 years ago

  • Legacy Backlogs Release (now unused) set to 166

Also available in: Atom PDF