Resource group tests

Edit online

There are two groups of resource group tests that can be run. Which group of tests run depends on the startup policy for the resource group: non-concurrent and concurrent resource groups. If a resource of the specified type does not exist in the resource group, the tool logs an error in the Cluster Test Tool log file.

Resource group starts on a specified node

The following tests run if the cluster includes one or more resource groups that have a startup management policy other than Online on All Available Nodes, that is, the cluster includes one or more non-concurrent resource groups.

The Cluster Test Tool runs each of the following tests in the order shown for each resource group:

Bring a resource group offline and online on a node.
```
RG_OFFLINE, RG_ONLINE
```

Bring a local network down on a node to produce a resource group fallover.

NETWORK_DOWN_LOCAL, rg_owner, svc1_net, Selective fallover on local
network down

Recover the previously failed network.

NETWORK_UP_LOCAL, prev_rg_owner, svc1_net, Recover previously failed
network

Move a resource group to another node. RG_MOVE
Bring an application controller down and recover from the application failure.
```
SERVER_DOWN, ANY, app1, /app/stop/script, Recover from
application failure
```

Resource group starts on all available nodes

If the cluster includes one or more resource groups that have a startup management policy of Online on All Available Nodes, that is, the cluster has concurrent resource groups, the tool runs one test that brings an application controller down and recovers from the application failure.

The tool runs the following test:

RG_OFFLINE, RG_ONLINE
SERVER_DOWN, ANY, app1, /app/stop/script, Recover from
application failure