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 1052713 - [RFE] Need additional supported database deployment options for Satellite 6 installation: such as External Postgres (and Managed Postgres?)
Summary: [RFE] Need additional supported database deployment options for Satellite 6 i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.4.0
Assignee: Martin Bacovsky
QA Contact: Ales Dujicek
URL:
Whiteboard:
: 1331533 1338977 (view as bug list)
Depends On: 1563211
Blocks: 260381 1052712 GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-01-13 22:15 UTC by Mike McCune
Modified: 2022-03-13 13:53 UTC (History)
33 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 15:25:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19667 0 High Closed Need additional supported database deployment options for Katello installation: such as External Postgres 2020-10-27 03:50:04 UTC
Foreman Issue Tracker 20550 0 Normal Closed backup & restore do not work with remote DB 2020-10-27 03:50:04 UTC
Foreman Issue Tracker 22886 0 Normal Closed Move katello-restore to foreman-maintain 2020-10-27 03:50:20 UTC
Red Hat Bugzilla 1052712 0 medium CLOSED Need documented procedure for setting up external database configuration 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1484067 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Knowledge Base (Solution) 2139431 0 None None None 2016-05-04 06:24:32 UTC
Red Hat Product Errata RHSA-2018:2927 0 None None None 2018-10-16 15:27:08 UTC

Internal Links: 1052712 1484067

Description Mike McCune 2014-01-13 22:15:33 UTC 
The Foreman installer has an option to specify the remote database host where postgres (or others) live:


--foreman-db-host

we need this to also be used when configuring the database the Katello engine uses as well as Candlepin.

This will allow us to support a database server that isn't the same machine as the Satellite 6 instance.
Comment 2 Xixi 2014-07-24 16:44:59 UTC 
(In reply to Mike McCune from comment #0)
> The Foreman installer has an option to specify the remote database host
> where postgres (or others) live:
> 

Hi Mike, just to clarify/follow up from IRC, is this BZ only for external Postgres DB - or Managed Postgres and External Oracle as well (i.e. all options currently offered as of Satellite 5.6 [1])?

There's been questions from support about customers who're on Satellite 5.6 with external dbs (Postgres or Oracle) about how to transition while keeping their db setup.

Thanks,
Xixi

[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/5.6/html-single/Installation_Guide/index.html#sect-Installation_Guide-Hardware_Requirements
Comment 11 Bryan Kearney 2016-04-29 12:04:58 UTC 
*** Bug 1331533 has been marked as a duplicate of this bug. ***
Comment 12 Sai Kiran Kanuri 2016-05-03 10:19:16 UTC 
Please also do add gutterball to the list of DB's that need to have support to be on external DB's.
Comment 16 Bryan Kearney 2016-05-27 18:42:26 UTC 
*** Bug 1338977 has been marked as a duplicate of this bug. ***
Comment 30 Martin Bacovsky 2017-05-25 09:29:54 UTC 
Created redmine issue http://projects.theforeman.org/issues/19667 from this bug
Comment 36 Satellite Program 2017-08-08 22:02:05 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19667 has been resolved.
Comment 37 Martin Bacovsky 2017-08-09 12:23:59 UTC 
Moving back to Assigned due to some pending work on backup & restore.
Comment 38 Satellite Program 2017-08-09 14:01:56 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19667 has been resolved.
Comment 39 Martin Bacovsky 2017-08-10 16:34:11 UTC 
Adding upstream issue for tracking progress on support for remote db in backup and restore scripts
Comment 45 Satellite Program 2018-04-20 16:01:43 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20550 has been resolved.
Comment 48 Satellite Program 2018-04-26 12:01:49 UTC 
Upstream bug assigned to jomitsch
Comment 53 Satellite Program 2018-05-18 10:01:45 UTC 
Upstream bug assigned to mbacovsk
Comment 54 Satellite Program 2018-05-18 10:01:57 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19667 has been resolved.
Comment 55 Rich Jerrido 2018-08-16 15:40:02 UTC 
Updating $SUBJECT to be clear to what is being delivered. Satellite will ship with support for an external PostgreSQL database. 

Support for Oracle databases are NOT planned for a near-term release of Satellite 6.
Comment 59 errata-xmlrpc 2018-10-16 15:25:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927
Note You need to log in before you can comment on or make changes to this bug.