The track parameter validation hook (introduced in #2144) runs validators as part of rally race, inside the actor system, just before the benchmark starts. This means a bad parameter is only reported after Rally bootstraps the actor system, and the error is shown as a traceback rather than a clean message.
This issue tracks adding a --validate flag that runs the registered validators for the selected challenge and then exits, without provisioning a cluster or running the benchmark.
The proposal is to run the validators in the main process before the actor system starts, reusing the existing params.invoke_validators seam. Load the track, resolve the challenge, and run the validators. On success, print a short confirmation (e.g. "Track parameters for challenge [] are valid.") and exit zero; on failure, exit non-zero with the TrackConfigError message. This keeps the check fast, avoids any cluster contact, and gives a clean one-line error.
The track parameter validation hook (introduced in #2144) runs validators as part of
rally race, inside the actor system, just before the benchmark starts. This means a bad parameter is only reported after Rally bootstraps the actor system, and the error is shown as a traceback rather than a clean message.This issue tracks adding a
--validateflag that runs the registered validators for the selected challenge and then exits, without provisioning a cluster or running the benchmark.The proposal is to run the validators in the main process before the actor system starts, reusing the existing
params.invoke_validatorsseam. Load the track, resolve the challenge, and run the validators. On success, print a short confirmation (e.g. "Track parameters for challenge [] are valid.") and exit zero; on failure, exit non-zero with the TrackConfigError message. This keeps the check fast, avoids any cluster contact, and gives a clean one-line error.