Bug 728041
Summary: | ccs --start/--stop should not change chkconfig services | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Etsuji Nakai <enakai> |
Component: | ricci | Assignee: | Chris Feist <cfeist> |
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | cluster-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-08 21:56:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Etsuji Nakai
2011-08-04 01:32:04 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. 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? 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. 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. |