Project

General

Profile

Actions
Copy link

Bug #34438

closed

Satellite upgrade failed with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass"

Added by Evgeni Golov about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Evgeni Golov
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
2053395
Pull request:
https://github.com/theforeman/foreman_maintain/pull/587
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2053395

Description of problem: Satellite upgrade failed with error "Couldn't connect to the server: undefined method `to_sym' for nil:NilClass"

Version-Release number of selected component (if applicable):
7.0

How reproducible:
always

Steps to Reproduce:
1. Restore Satellite 6.10.z by using the backup data.
2. Setup the repository to perform the satellite upgrade.
3. Run the upgrade from 6.10.z to 7.0
foreman-maintain upgrade run --target-version 7.0 -y
.....
.....
Running Checks after upgrading to Satellite 7.0 ================================================================================
Clean old Kernel and initramfs files from tftp-boot: [32m[1m[OK][0m
--------------------------------------------------------------------------------
Check number of fact names in database: [32m[1m[OK][0m
--------------------------------------------------------------------------------
Check whether all services are running: [32m[1m[OK][0m
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [31m[1m[FAIL][0m
Couldn't connect to the server: undefined method `to_sym' for nil:NilClass
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]? (assuming yes)

Actual results:
Satellite upgrade failed in post-upgrade check with "undefined method `to_sym' for nil:NilClass " error.

Expected results:
Satellite upgrade should be completed successfully.

Additional info:

Actions
Copy link
 #1

Updated by The Foreman Bot about 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Evgeni Golov
  • Pull request https://github.com/theforeman/foreman_maintain/pull/587 added
Actions
Copy link
 #2

Updated by Evgeni Golov about 3 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF