Upgrade Cluster Validation Suite (CVS) to the latest version

Upgrade Cluster Validation Suite (CVS) to the latest version#

2026-09-25

4 min read time

Applies to Linux

Upgrade CVS after pulling the latest source from the repository. Follow the method that matches how you originally installed CVS.

Identify how CVS was installed#

To identify how CVS was installed, use these commands from the cloned CVS on the head node (they don’t require an active venv):

Command

Installation via

ls .cvs_venv/bin/cvs

Makefile (make install) if the command is succesful

ls <venv>/bin/cvs

pip into a virtual environment if the command succeeds for a venv you created

docker images cvs

Docker image if the command lists cvs:local (or the tag you used)

If a venv is already active, you can also run:

which cvs
pip show cvs

Typical which cvs paths when a venv is active:

  • .../cvs/.cvs_venv/bin/cvs — Makefile

  • Another .../bin/cvs path — custom pip venv

Note

which cvs only works if a virtual environment is already active (or cvs is otherwise on PATH). An empty result often means the venv is not activated, not that CVS is missing.

CVS upgrade paths#

If installed with make install#

cd /path/to/cvs/source
git pull
make install
source .cvs_venv/bin/activate

If installed manually in a custom venv#

cd /path/to/cvs/source
git pull
python setup.py sdist
pip install --upgrade dist/cvs*.tar.gz

If installed as a Docker image#

Rebuild the image from the updated source:

cd /path/to/cvs/source
git pull
docker build --tag cvs:local .
docker run --rm cvs:local --version

The new image replaces the old one locally. If you use a named container (cvs-head), stop and remove it before rebuilding so the new image is used on the next docker run.

Verify#

Run the following commands to verify the upgrade. Activate the venv first if you installed with Makefile or pip. For a Docker install, use docker run --rm cvs:local --version and docker run --rm cvs:local list.

cvs --version
cvs list

Expected output (suite names and totals vary by version):

(.cvs_venv) user@head-node:~/cvs$ cvs --version
cvs: 0.2.0

(.cvs_venv) user@head-node:~/cvs$ cvs list

Available Tests
================================================================================

Package: cvs
--------------------------------------------------------------------------------

  cvs.tests.health (4 test suites)
    • agfhc_cvs
    • csp_qual_agfhc
    • rvs_cvs
    • transferbench_cvs

  cvs.tests.health.install (5 test suites)
    • install_agfhc
    • install_babelstream
    • install_rocblas
    • install_rvs
    • install_transferbench

  cvs.tests.ibperf (2 test suites)
    • ib_perf_bw_test
    • install_ibperf_tools
<<truncated>>
================================================================================
Total: 48 test suites across 1 package(s)

If cvs --version prints the updated version number and cvs list shows available test suites, the upgrade was successful.

Next steps#

Contents