Use this procedure to finish validating the success of rebuilt NCNs.
Confirm what the Configuration Framework Service (CFS) configurationStatus is for the desiredConfig after rebooting the node.
NOTE The following command will indicate if a CFS job is currently in progress for this node.
IMPORTANT: The following command assumes that the variables from the prerequisites section have been set.
cray cfs components describe $XNAME --format json
Example output:
{
"configurationStatus": "configured",
"desiredConfig": "ncn-personalization-full",
"enabled": true,
"errorCount": 0,
"id": "x3000c0s7b0n0",
"retryPolicy": 3,
}
If the configurationStatus is pending, wait for the job to finish before continuing. If the configurationStatus is failed, this means the failed CFS job
configurationStatus should be addressed now for this node. If the configurationStatus is unconfigured and the NCN personalization procedure has not been done
as part of an install yet, this can be ignored.
If configurationStatus is failed, See
Troubleshoot Ansible Play Failures in CFS Sessions for how to analyze the pod logs
from cray-cfs to determine why the configuration may not have completed.
Collect data about the system management platform health (can be run from a master or worker NCN).
/opt/cray/platform-utils/ncnHealthChecks.sh
/opt/cray/platform-utils/ncnPostgresHealthChecks.sh
Return to the main Rebuild NCNs page.