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
Hi Ashish, We currently do raise a warning if the capsule is self-registered. https://github.com/theforeman/foreman_maintain/blob/master/definitions/checks/system_registration.rb So I suppose, the warning should actually be a `failure` and restrict user/admin from upgrading satellite or capsule. And, this seems to be duplicate BZ https://bugzilla.redhat.com/show_bug.cgi?id=1545136.
Hi Swapnil, Correct, the upgrade should fail and should not continue. Yeah BZ 1545136 is duplicate of this bugzilla, so we can keep only one. Regards, Ashish
*** Bug 1545136 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/22578 from this bug
Upstream bug assigned to apatel
Upstream bug assigned to sabnave
No customers reported this issue for a long time so I do not think we need to fix this issue anymore. After closing this bz, if any customers report then we can think of re-considering.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days