Project

General

Profile

Bug #17804

upgrade to 3.2.1 fails when pulpnode_enabled not defined

Added by Chris Duryee over 5 years ago. Updated almost 4 years ago.

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

Description

If 'pulpnode_enabled' is not defined in the foreman proxy plugin answers, upgrades will fail.

It looks like this line is attempting to determine if the system is a capsule or katello:

  capsule = @kafo.param('foreman_proxy_plugin_pulp', 'pulpnode_enabled').value

The failure is:


/usr/share/katello-installer-base/hooks/pre/30-upgrade.rb:107:in `block (4 
 levels) in load': undefined method `value' for nil:NilClass (NoMethodError)
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:34:in 
 `instance_eval'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:34:in `block 
 (4 levels) in load'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hook_context.rb:13:in 
 `instance_exec'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hook_context.rb:13:in 
 `execute'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:51:in `block 
 in execute'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:49:in `each'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:49:in `execute'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:408:in 
 `run_installation'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:147:in 
 `execute'
     from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
     from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
     from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:154:in 
 `run'
     from /sbin/foreman-installer:8:in `<main>'

History

#1 Updated by Justin Sherrill over 5 years ago

  • Legacy Backlogs Release (now unused) set to 214

#2 Updated by Justin Sherrill over 5 years ago

  • Legacy Backlogs Release (now unused) changed from 214 to 222

#3 Updated by Justin Sherrill almost 5 years ago

  • Legacy Backlogs Release (now unused) deleted (222)

#4 Updated by Justin Sherrill almost 5 years ago

  • Status changed from New to Rejected
  • Legacy Backlogs Release (now unused) set to 166

closing, as no users have complained about this.

Also available in: Atom PDF