Project

General

Profile

Bug #19698

Katello upgrade 3.3 to 3.4 problem

Added by Tommy Fallsen almost 5 years ago. Updated almost 4 years ago.

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

Description

Hi
I got this error during upgrade. Anyone know how to fix it?
Failed to call refresh: Proxy -DUMMY-NAME-m cannot be refreshed: unknown error (response 500)
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[-DUMMY-NAME-m]: Proxy -DUMMY-NAME-m cannot be refreshed: unknown error (response 500)

More of the log in atachment

katello.txt katello.txt 15.2 KB production.log Tommy Fallsen, 06/01/2017 01:10 AM

History

#1 Updated by Justin Sherrill almost 5 years ago

  • Status changed from New to Need more information
  • Legacy Backlogs Release (now unused) changed from 211 to 228

I do not see any attachment, was it forgotten?

We need /var/log/foreman/production.log to try to figure this one out. Thanks

#3 Updated by Mario Gamboa almost 5 years ago

try using the option --foreman-proxy-register-in-foreman "false" and after upgrade modify the files needed as per bug reported http://projects.theforeman.org/issues/19329

#4 Updated by Eric Helms almost 5 years ago

  • Legacy Backlogs Release (now unused) changed from 228 to 258

#5 Updated by Justin Sherrill almost 5 years ago

Tommy, that looks like the installer log, we need the /var/log/foreman/production.log right after an installer run attempt.

#6 Updated by Justin Sherrill almost 5 years ago

  • Legacy Backlogs Release (now unused) changed from 258 to 166

#7 Updated by Eric Helms almost 5 years ago

  • Status changed from Need more information to Closed

If you are still seeing this issue as of Katello 3.4, please re-open for us to consider.

Also available in: Atom PDF