Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1998147

Summary: The steps to upgrade Satellite 6.10 with external database should be included in the Satellite upgrade documentation for Satellite 6.10
Product: Red Hat Satellite Reporter: Jayant Bhatia <jbhatia>
Component: UpgradesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.0CC: agadhave, bangelic, ehelms, gpayelka, ifowler, jpasqual, karnsing, ktordeur, mdolezel, ramsingh, ryandeussing, wpinheir
Target Milestone: UnspecifiedKeywords: Documentation, Reopened, Triaged
Target Release: UnusedFlags: gpayelka: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-18 13:35:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jayant Bhatia 2021-08-26 13:29:53 UTC
Document URL: 
In our current Satellite documentation, we do not have the steps mentioned anywhere to upgrade Satellite with external postgres and mongodb configured.

Describe the issue:
We have multiple customers who are using Satellite with external postgres and mongodb in place. When they are upgrading Satellite, they do not find the right steps listed in the documentation and open a support case looking for the steps to upgrade Satellite with external db. 

Suggestions for improvement: 
In Satellite-6.10 documentation which will be coming later, it would be great if we can have separate section which talks about detailed steps to upgrade Satellite with external db.

Comment 5 Marie Hornickova 2022-01-03 11:52:54 UTC
*** Bug 2022341 has been marked as a duplicate of this bug. ***

Comment 6 Jayant Bhatia 2022-01-05 14:31:08 UTC
@jpasqual : Sorry to directly tag you here. Just wanted to check if you have any inputs to provide here? We are looking for the steps to upgrade Satellite with external DB, so the same can be included in our documentation.

Comment 7 Kenny Tordeurs 2022-01-05 14:37:18 UTC
Steps are most likely: https://github.com/theforeman/foreman-documentation/commit/a418ce4923836ee407948e488ab83411137d7c50

Best to get engineering/dev to confirm what is really needed.

Comment 8 Jayant Bhatia 2022-01-12 12:56:45 UTC
@Ian : As mentioned by Kenny, it would be great if we can have someone from engineering confirm the steps: https://github.com/theforeman/foreman-documentation/commit/a418ce4923836ee407948e488ab83411137d7c50

Comment 10 Ganesh Payelkar 2022-06-23 11:46:09 UTC
Re-opening this doc bug as instruction added in the documentation is for the new installation not for upgrading satellite when we have external DB. 

Expecting : 

1) what steps do we need to take before upgrading the satellite server when the database is configured on a remote server. 
2) Any prerequisites to follow before upgrading the database?
3) Does the satellite upgrade need an option to add in 'foreman-maintain upgrade run --target-version 6.x' ?

Comment 15 Brad Buckingham 2022-10-06 13:19:20 UTC
*** Bug 2131539 has been marked as a duplicate of this bug. ***

Comment 19 Eric Helms 2024-01-18 13:35:54 UTC
This only applies to Satellite 6.10, and since it is EOL we are opting to close this issue.

Comment 20 Red Hat Bugzilla 2024-05-18 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days