Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In section "5.9. Adding a Cluster Service to the Cluster" we talk about autostart, we need to specify that setting it to '1' enables it (which is the default). And setting it to anything else disables it.
Version-Release number of selected component (if applicable):
In RHEL 6.1
This isn't a critical issue, but we'd like to fix it as soon as time is available.
I would make these changes:
autostart — Specifies whether to autostart the service when the cluster starts.
should be changed to something like this:
autostart — Specifies whether to autostart the service when the cluster starts. (Use '1' to enable, '0' to disable, default is enabled).
I'm assigning this to me and dev_acking this because autostart is covered in the Cluster Administration guide.
I'll make a note here to check whether it's covered in the Overview as well, but it's definitely in the Cluster Administration document.