Bug 1526130 - Satellite 6 High Availability Tracker
Summary: Satellite 6 High Availability Tracker
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Other
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 1243954 1337451 (view as bug list)
Depends On:
Blocks: Sat6_HA_Tracker
TreeView+ depends on / blocked
 
Reported: 2017-12-14 19:55 UTC by Rich Jerrido
Modified: 2022-03-13 14:35 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-12 07:51:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1196002 0 medium CLOSED [RFE] Support active-active Satellite 6 configurations 2023-03-24 13:30:55 UTC
Red Hat Bugzilla 1243954 0 unspecified CLOSED [RFE] Separate Satellite 6 Components For Scalability and High Availability 2022-03-13 14:12:54 UTC

Internal Links: 1196002 1243954

Description Rich Jerrido 2017-12-14 19:55:58 UTC

Comment 3 Rich Jerrido 2018-07-05 15:21:07 UTC
*** Bug 1243954 has been marked as a duplicate of this bug. ***

Comment 4 Rich Jerrido 2018-07-18 12:28:21 UTC
*** Bug 1337451 has been marked as a duplicate of this bug. ***

Comment 6 Ashish Humbe 2019-02-12 07:51:24 UTC
With the release of Red Hat Satellite 6.4, it provides Load Balanced capsule feature. To implement it follow the documentation guide: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html-single/load_balancing_guide/


There are no plans to provide HA solution for Satellite 6 in near future so customers are recommended to virtualize the Satellite and Capsule servers and use the hypervisor tools to provide high availability of the virtual machine hosting the Satellite or Capsule.

For more details refer: https://access.redhat.com/solutions/3402361


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