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:
While upgrading capsule from 6.4 to 6.5 upgrade failed with
/usr/share/gems/gems/kafo-2.1.0/lib/kafo/hook_context.rb:71:in `module_enabled?': undefined method `enabled?' for nil:NilClass (NoMethodError)
Version-Release number of selected component (if applicable):
Satellite 6.5 snap 2.0
How reproducible: always
Steps to Reproduce:
1. yum update on capsule
2. satellite-installer --scenario capsule --upgrade
Actual results: Upgrade failed with error
Done [100%]Installing Done [100%]
The full log is at /var/log/foreman-installer/capsule.log
/usr/share/gems/gems/kafo-2.1.0/lib/kafo/hook_context.rb:71:in `module_enabled?': undefined method `enabled?' for nil:NilClass (NoMethodError)
from /usr/share/katello-installer-base/hooks/post/30-upgrade.rb:45:in `block (4 levels) in load'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hooking.rb:34:in `instance_eval'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hooking.rb:34:in `block (4 levels) in load'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hook_context.rb:16:in `instance_exec'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hook_context.rb:16:in `execute'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hooking.rb:51:in `block in execute'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hooking.rb:49:in `each'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/hooking.rb:49:in `execute'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:476:in `block in run_installation'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/exit_handler.rb:29:in `call'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/exit_handler.rb:29:in `exit'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:169:in `exit'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:475:in `run_installation'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:156:in `execute'
from /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:63:in `run'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:119:in `run'
from /usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:132:in `run'
from /usr/share/gems/gems/kafo-2.1.0/lib/kafo/kafo_configure.rb:163:in `run'
from /usr/sbin/satellite-installer:8:in `<main>'
Expected results: Successful capsule upgrade.
Additional info:
Comment 3Ewoud Kohl van Wijngaarden
2018-11-03 12:48:09 UTC
VERIFIED
Version tested:
Satellite 6.5 snap 6
satellite-capsule-6.5.0-5.beta.el7sat.noarch
Datacat_fragment[foreman_proxy::enabled_features:: [99%]Installing Service[smart_proxy_dynflow_core] [99%]Installing Done [100%]Installing Done [100%]
The full log is at /var/log/foreman-installer/capsule.log
Upgrade completed!
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/RHSA-2019:1222