Hide Forgot
ccs --status uptime field is sometimes blank Version-Release number of selected component (if applicable): ccs --status output after rebooting a cluster member can be blank. It's been reliably blank in my testing, but I'm unsure that I've found all of the possible preconditions. in this example, north-16 is a cluster node, and the uptime field was populated & accurate before it was rebooted. After reboot, uptime is empty: -(~:$)-> ccs -h north-14 --status <cluster alias="test-00" cluster_version="6" config_version="8" minQuorum="2" name="test-00" quorate="true" votes="3"> <node clustered="true" name="north-14" nodeid="1" online="true" uptime="156851" votes="1"/> <node clustered="true" name="north-15" nodeid="2" online="true" uptime="71819" votes="1"/> <node clustered="true" name="north-16" nodeid="3" online="true" uptime="" votes="1"/> </cluster> just to be certain: -(~:$)-> clustat Cluster Status for test-00 @ Fri Apr 1 11:04:04 2011 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ north-14 1 Online, Local north-15 2 Online north-16 3 Online all nodes have been up several minutes Expected results: Accurately populated uptime field
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Moving this to 6.2 since --status is not support in 6.1 ccs. If we decide to support it in 6.2 we will get this fixed.
ccs --status is still not going to be support in 6.2, bumping this to 6.3
Closing because ccs --status is not currently being supported, we may add it in the future, but for now we don't have it.