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 728041 - ccs --start/--stop should not change chkconfig services
Summary: ccs --start/--stop should not change chkconfig services
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ricci
Version: 6.1
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-04 01:32 UTC by Etsuji Nakai
Modified: 2011-09-13 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-08 21:56:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Etsuji Nakai 2011-08-04 01:32:04 UTC 
Description of problem:
When starting and stopping the cluster using ccs --start/--stop, chkconfig services are changed on/off accordingly. But it'd be better not to change the chkconfig status. It should just start/stop the services.

The problem is regarding the following scenario.

In the customer's cluster:

- They start/stop the cluster with starting/stopping the services directly.(Not using ccs at the moment.)
- They set chkconfig off for the cluster services (cman, rgmanger etc.)
- They force-reboot the failed node with the fence device.

In this setting, when a node is force-rebooted with some problem such as kernel panic, for example, the node doesn't automatically join the cluster. Then the customer logs-in to the node and investigates the problem. When they are sure that the problem is resolved, they start the cluster services on this node again.

Now, the problem is that this customer cannot adopt the new ccs tool for the cluster operation. Under the ccs operation, when the failed node is force-rebooted, it automatically tries to join the cluster as chkcfonig is on although the potential problem is not yet investigated and resolved by the customer. It's not desirable to get the failed node to join the cluster automatically.
Comment 3 Chris Feist 2011-08-08 21:56:58 UTC 
Unfortunately, this works as designed (and I believe this is exactly how luci does it as well).  When you stop a node, you're permanently stopping it until you want to manually bring it back into service.

When you manually stop a node, you need to manually start it back up again.

There may be room for some documentation improvement.  I'll take a look at it and see if I need to file a bug to specify that the --start & --stop enable/disable cluster nodes.
Comment 4 Etsuji Nakai 2011-08-08 22:14:08 UTC 
No, the problem is not that I need to manually start the node.

The problem is that once I started the node with --start, it automatically starts again when it is force-rebooted by the fence device. Don't you think it is a bad design that a failed (force-rebooted) node automatically joins the cluster again?
Comment 5 Chris Feist 2011-08-08 22:58:57 UTC 
I think the issue is that --start/--stop should really be called --enable&start --disable&stop.  ccs just calls ricci/clustermon and ricci/clustermon executes the command.  Currently there is no command in ricci/clustermon for only starting or stopping without turning the service on/off.

This will definitely work differently on RHEL7, but right now this behavior is consistent with how things worked in RHEL4/5.
Comment 6 Etsuji Nakai 2011-08-08 23:50:55 UTC 
Yes, it makes sense. Logically, there could be the following combinations.

--enbale&start / --disable&stop => service start/stop & chkconfig on/off
--enable / --disable => chkconfig on/off
--start / --stop => service start/stop

I hope RHEL7 will allow customers to choose their preferred operation. Thanks.
Note You need to log in before you can comment on or make changes to this bug.