This test requires that the Cray CLI is configured on nodes where the test is executed. See Cray command line interface.
This test can be run on any Kubernetes NCN (any master or worker NCN, but not the PIT node). When run on a Kubernetes master NCN, the TFTP file transfer subtest is omitted. However, that TFTP subtest is run on a worker NCN as part of the Goss NCN health checks.
(ncn-mw#
) The following command runs the entire SMS test suite (with the possible exception of the TFTP file
transfer subtest, as noted in the previous paragraph).
/usr/local/bin/cmsdev test -q all
cmsdev
tool logs to /opt/cray/tests/install/logs/cmsdev/cmsdev.log
/opt/cray/tests/cmsdev.log
cmsdev
resultsSUCCESS
.
SUCCESS: All 6 service tests passed: bos, cfs, conman, ims, tftp, vcs
FAILURE
and lists the failed checks.
FAILURE: 2 service tests FAILED (conman, ims), 4 passed (bos, cfs, tftp, vcs)
all
in the cmsdev
command line with the name of the service. For example: /usr/local/bin/cmsdev test -q cfs
Additional test execution details can be found in /opt/cray/tests/install/logs/cmsdev/cmsdev.log
.
Some of the subtests may fail if the Cray CLI is not configured on the management NCN where cmsdev
is executed.
See the following for more information:
On systems where too many BOS v1 sessions exist, the cmsdev
test will hang when trying to
list BOS v1 sessions. See Hang Listing BOS V1 Sessions for more
information.
On CSM 1.5.0 systems with a lot of nodes, the CFS subtest may report errors that look similar to the following:
ERROR (run tag qdthp-cfs): GET https://api-gw-service-nmn.local/apis/cfs/v2/components: expected status code 200, got 400
ERROR (run tag qdthp-cfs): CLI command (cfs components list --format json) failed with exit code 2
For more details, see CFS V2 Failures On Large Systems.