Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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