Software Management Services Health Check - Known Issues

This document describes known issues and troubleshooting guidance for the cmsdev test suite used to validate Software Management Services (SMS) in CSM.

For comprehensive documentation including all available tests, command-line options, and usage examples, see cmsdev Tests.

Quick reference

(ncn-mw#) The following command runs the SMS health checks:

/usr/local/bin/cmsdev test -q all

(ncn-mw#) Show the cmsdev version by running the following command:

/usr/local/bin/cmsdev version

The test log location is: /opt/cray/tests/install/logs/cmsdev/YYMMDD_HHMMSS_microseconds_PID/cmsdev.log

For detailed usage information, see cmsdev Tests.

Known issues

This section documents common issues that may occur when running the cmsdev test suite.

  1. Cray CLI not configured
  2. Invalid CFS component
  3. VCS subtest command failure

1. Cray CLI not configured

1.1 Symptom

Some subtests fail with CLI-related errors.

1.2 Cause

The Cray CLI is not properly configured on the management NCN where cmsdev is executed.

1.3 Resolution

Configure the Cray CLI before running tests. For information on how to do this, see the following resources:

Note: CLI tests are only run when using the --include-cli flag. See Test control options for details.

2. Invalid CFS component

2.1 Symptom

The cmsdev CFS subtest fails with errors related to component ID validation.

The error messages vary by cmsdev version:

See Quick reference for details on how to check the cmsdev version

  • cmsdev versions 1.25 or higher:

    ERROR (run tag fhn3C-cfs): In first item listed, 'id' field maps to a 0-length string, but it should have non-0 length

  • cmsdev versions 1.16.2 to 1.24:

    ERROR (run tag sosdD-cfs): GET https://api-gw-service-nmn.local/apis/cfs/v3/components/: expected status code 200, got 404
ERROR (run tag sosdD-cfs): GET https://api-gw-service-nmn.local/apis/cfs/v2/components/: expected status code 200, got 404
ERROR (run tag sosdD-cfs): CLI command (cfs v3 components describe  --format json) failed with exit code 2
ERROR (run tag sosdD-cfs): CLI command (cfs v2 components describe  --format json) failed with exit code 2

  • cmsdev versions less than 1.16.2:

    ERROR (run tag fhn3C-cfs): First list item has empty value for "id" field

2.2 Cause

A CFS component exists with a zero-length string for its id field.

2.3 Resolution

See CFS Component With Zero-Length ID for detailed remediation steps.

3. VCS subtest command failure

3.1 Symptom

The VCS subtest fails with a command error.

The error message resembles the following:

ERROR (run tag Xe9tC-vcs): Command failed

If the test is run in verbose mode, or the cmsdev log file is examined, a line similar to the following is found:

fatal: unable to access 'https://crayvcs:BPuN/M846JL5XKTTWVqcV2mhuZfzOC64nnZ/e54ri1M=@api-gw-service-nmn.local/vcs/test-cmsdev-zvkEP50G/harf-zEK1SuiP.git/': URL using bad/illegal format or missing URL
  • In order to run the test in verbose mode, include the -v flag (e.g./usr/local/bin/cmsdev test -v vcs)
  • The log file is located in a timestamped subdirectory: /opt/cray/tests/install/logs/cmsdev/YYMMDD_HHMMSS_microseconds_PID/cmsdev.log
    • See Logging for more information on cmsdev logging

3.2 Cause

The VCS administrative password contains illegal characters that are not properly URL-encoded.

3.3 Resolution

See VCS Password With Illegal Characters for detailed remediation steps.

Additional resources