RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 801894 - 'Red Hat Cluster Suite' name is incorrect
Summary: 'Red Hat Cluster Suite' name is incorrect
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-firewall
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 947782
TreeView+ depends on / blocked
 
Reported: 2012-03-09 18:54 UTC by Lon Hohberger
Modified: 2014-04-03 12:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-03 12:21:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lon Hohberger 2012-03-09 18:54:28 UTC 
Description of problem:

* Cluster Suite was a RHEL add-on in the RHEL3/4 products; it is called the 'High Availability Add-On' in RHEL5.5+/6+

* The port assignments look correct, although the documentation states that 
  16851/TCP should also be opened.

Version-Release number of selected component (if applicable): system-config-firewall-1.2.27-5.el

Actual results:
  '[ ] Red Hat Cluster Suite'

Expected results:
  '[ ] Red Hat High Availability'
Comment 2 RHEL Program Management 2012-09-07 04:58:46 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 3 Lon Hohberger 2013-04-25 14:13:06 UTC 
I think you can close this.  IIRC, the name is also represented in the CLI tools, and breaking CLI is not worth it.
Comment 4 Thomas Woerner 2013-04-25 14:21:30 UTC 
All parts of system-config-firewall are using this for cli and gui:

    _Service("cluster-suite", _("Red Hat Cluster Suite"), [
            # corosync/openais
            (5404, "udp"), (5405, "udp"),
            # ricci
            (11111, "tcp"),
            # dlm
            (21064, "tcp"),
            ],
             _("This option allows you to use the Red Hat Cluster Suite. "
               "Ports are opened for openais, ricci and dlm. You need the "
               "Red Hat Cluster Suite installed for this option to be "
               "useful.")),

If we change it, it will get changed everywhere in system-config-firewall.

I have just seen that also the tag of the entry is "cluster-suite". If we change this, then the use of the old name will result in an error. Is it documented (by us or externally) to use "cluster-suite"?
Comment 5 Lon Hohberger 2013-04-25 14:36:07 UTC 
This is what we document (which perhaps isn't ideal; not sure):

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Cluster_Administration/index.html#s2-iptables_firewall-CA

However, I think that there's risk that someone is using kickstart (or whatever) and system-config-firewall (lokkit, really) in deployment scripts.  That's what I didn't consider when I filed this bug.

e.g.
  # lokkit -s cluster-suite

I'd be worried that changing this would break someone's deployment scripts.
Comment 9 Thomas Woerner 2014-04-03 12:21:47 UTC 
Closing as NOT A BUG due to comment #5.
Note You need to log in before you can comment on or make changes to this bug.