You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
roachtest/mixedversion: sync workload binary versions with the cluster version
The current workload binary is no longer backwards compatible for certain
workloads. Previously, the workload binary would just use whatever default
binary was staged on the workload node. Currently, there's a quick fix that
installs the current system version's binary on the workload node when a
workload cmd is being executed.
This change bakes that behavior into the test framework itself, so we can remove
the binary staging from the Workload hook. Workload nodes are staged with all
versioned binaries in the upgrade plan so all workload commands can use a
versioned binary that matches the current state of the cluster.
Resolves#147374
Epic: None
Release note: None
Use this option to disable specific [mutators](#mutators) that are incompatible with the test.
391
391
392
+
```go
393
+
mixedversion.WithWorkloadNodes(c.WorkloadNode())
394
+
```
395
+
Certain workloads i.e. bank are no longer backwards compatible as of 25.3. Therefore a new best practice for using
396
+
using workload during your test is to execute a workload command on a binary that matches the cluster version. Using
397
+
this option tells the framework to handle staging all the binaries you need for your test on the workload node(s)
398
+
during test setup.
399
+
392
400
### Deployment Modes
393
401
394
402
By default, each run of a `mixedversion` test happens in one of 3 possible _deployment modes_: `system-only`, `shared-process`, and `separate-process`. In the latter two options, the framework will create a test tenant, and tests should exercise the feature they are testing by invoking it on the tenant.
0 commit comments