Bug 1544769 - foremain-maintain should validate whether satellite is self registered or not, before starting upgrade.
Summary: foremain-maintain should validate whether satellite is self registered or not...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.3.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Swapnil Abnave
QA Contact: Jameer Pathan
URL:
Whiteboard:
: 1545136 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-13 13:31 UTC by Ashish Humbe
Modified: 2023-09-15 00:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 13:09:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22578 0 High Ready For Testing foremain-maintain should validate whether satellite is self registered or not, before starting upgrade. 2020-12-11 10:24:07 UTC

Description Ashish Humbe 2018-02-13 13:31:13 UTC
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

Comment 2 Swapnil Abnave 2018-02-14 11:12:19 UTC
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.

Comment 3 Ashish Humbe 2018-02-14 11:15:22 UTC
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

Comment 4 Swapnil Abnave 2018-02-14 11:17:31 UTC
*** Bug 1545136 has been marked as a duplicate of this bug. ***

Comment 5 Swapnil Abnave 2018-02-14 11:21:17 UTC
Created redmine issue http://projects.theforeman.org/issues/22578 from this bug

Comment 6 Satellite Program 2018-02-14 13:28:55 UTC
Upstream bug assigned to apatel

Comment 8 Satellite Program 2018-03-20 00:27:20 UTC
Upstream bug assigned to sabnave

Comment 9 Satellite Program 2018-06-07 14:25:12 UTC
Upstream bug assigned to sabnave

Comment 11 Ashish Humbe 2021-05-18 13:09:13 UTC
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.

Comment 12 Red Hat Bugzilla 2023-09-15 00:06:29 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.