Project

General

Profile

Bug #22578

foremain-maintain should validate whether satellite is self registered or not, before starting upgrade.

Added by Swapnil Abnave almost 2 years ago. Updated about 1 year ago.

Status:
Ready For Testing
Priority:
High
Category:
Check
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

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

Description of problem:
From satellite v 6.3 onwards, we are not supporting self-registered satellite server, reference [1] and [2]

The foreman-maintain should add this check and notify the users accordingly in pre-upgrade check and ask customer follow upgrade steps for disconnected satellite server.

It will be nice if we could point the KCS / Doc link for the disconnected upgrade.

Version-Release number of selected component (if applicable):
Red Hat Satellite 6.3 Upgrade

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html/installation_guide/preparing_your_environment_for_installation#system_requirements

[2] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#migrating_a_self_registered_satellite

History

#1 Updated by Swapnil Abnave almost 2 years ago

  • Target version set to next version
  • Assignee changed from Anurag Patel to Swapnil Abnave
  • Category set to Check

#2 Updated by The Foreman Bot almost 2 years ago

  • Pull request https://github.com/theforeman/foreman_maintain/pull/142 added

#3 Updated by The Foreman Bot over 1 year ago

  • Pull request https://github.com/theforeman/foreman_maintain/pull/192 added

#4 Updated by Amit Upadhye over 1 year ago

  • Pull request deleted (https://github.com/theforeman/foreman_maintain/pull/142)

#5 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing

Also available in: Atom PDF