Description of problem: Using redhat-config-cluster-cmd to modify a running service quietly succeeds. Version-Release number: 1.0.1-4 (Sushi/RHEL3 U1 Beta) How reproducible: 100% Steps to Reproduce: 1. Start a clustered service 2. Modify with redhat-config-cluster-cmd Actual results: Modify succeeds. At this point, the service may not function properly. Expected results: Error returned. Modifying services known to be running should *not* succeed, as there is no previous record of service information. Additional Info: Hardy noted that the code is there, but isn't properly being executed.
Made a mistake earlier - the code is there, and it is working properly. Here is the output of the 'clustat' command which shows cluster status: Cluster Status - Red Hat Clumanager Cluster 13:47:20 Cluster Quorum Incarnation #1 Shared State: Shared Raw Device Driver v1.2 Member Status ------------------ ---------- localhost Active <-- You are here unicluster4 Inactive Service Status Owner (Last) Last Transition Chk Restarts -------------- -------- ---------------- --------------- --- -------- nfs_svc1 started localhost 13:21:09 Dec 22 50 0 And here is the output of 'redhat-config-cluster-cmd --service=nfs_svc1 --checkinterval=120', which is an attempt to change the service 'checkinterval' to 120: Error: Service must be disabled before updates can be made That output is correct - that redhat-config-cluster-cmd command failed. There was NO update made to service nfs_svc1.
So... does this bug exist or not? *confused*
No.