HomeSort by relevance Sort by last modified time
    Searched refs:that (Results 1 - 25 of 221) sorted by null

1 2 3 4 5 6 7 8 9

  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/recovery/others/
README 31 This subdir consists of tests for other NFSv4 tests that require
  /test/ontest-stc2/src/suites/share/tests/sharemgr/oneoff/
README 29 This directory holds sharemgr tests that are against bugs found
30 that really don't fit in any specific area, and may be quite intrusive
  /test/stcnv/usr/src/suites/fs/share/tests/sharemgr/oneoff/
README 29 This directory holds sharemgr tests that are against bugs found
30 that really don't fit in any specific area, and may be quite intrusive
  /test/ohacts/src/doc/dataservice/non_reboot/
test_6.txt 44 Verify that the resource groups are offline and that all the resources
47 Verify that all the daemons and fault monitor daemons for every
50 3. Verify that setup and client programs failed.
test_9.txt 41 1. Get the list of nodes that can be a master for FAILOVER_RG_1
47 Pick a node from 1) above that is not $primary_node. Store the
55 Verify that the resource groups are online and that all the resources
59 Verify that all the daemons and fault monitor daemons for every
62 3. Verify that client programs run correct.
test_3.txt 43 Verify that the resource groups are online and that all the resources
47 Verify that all the daemons and fault monitor daemons for every
50 3. Verify that setup and client programs run correct on the client node.
test_10.txt 47 3. Verify that the process is killed
49 4. Verify that the daemon process is restarted
55 6. Verify that the dataservice is failed over to another node.
test_4.txt 46 2. Verify that resource is disabled. But other resources
50 verify that the daemon processes and fault monitors are not running on
53 4. Use client program to verify that the resource is not available.
test_5.txt 46 2. Verify that resource is enabled. Also other resources
50 verify that the daemon processes and fault monitors are running on
53 4. Use client program to verify that the resource is available.
test_12.txt 48 3. Verify that the process is killed.
50 4. Verify that the daemon process is restarted
54 Verify that the resource groups are online and that all the resources
test_15.txt 44 Verify that the resource groups are removed.
  /test/ohacts/src/tset/geo/doc/assertions/
geo_avs_mult_pgs 42 With 2 PGs configured, verify that geopg switchover succeeds when AVS is
50 Issue 'geopg switchover' from <cluster-1> so that
53 Issue 'geopg switchover' from <cluster-2> so that
62 With 2 PGs configured, verify that 'geopg switchover'on pg that
63 has AVS set in REP mode passes, and 'geopg switchover' on pg that
72 Issue 'geopg switchover' on PG1 from <cluster-1> so that
74 Issue 'geopg switchover' on PG2 from <cluster-1> so that
77 Issue 'geopg switchover'on PG2 from <cluster-2> so that
87 For both PGs, verify that geopg takeover succeeds when AVS is i
    [all...]
geo_avs_reboot 43 Verify that if primary cluster went down, we can do 'geopg takeover'
46 Verify that we can restore the standby cluster, and do
47 'geopg switchover' back, so that pg will be primary-ed on
56 = Issue 'geopg takeover' on pg so that it will be primary-ed
60 = Issue 'geopg switchover' from <cluster-2> so that
69 Verify that if primary cluster went down, we can do 'geopg takeover'
72 After the standy cluster reboots back up, verify that we can restore
73 the standby cluster, and do 'geopg switchover' back, so that pg
81 = Issue 'geopg takeover' on pg so that it will be primary-ed on
86 = Issue 'geopg switchover' from <cluster-2> so that
    [all...]
geo_avs_mult_pgs_reboot 43 Verify that with 2 pgs, if primary cluster went down, we can do
46 After the standy cluster reboots back up, verify that we can restore
48 that pgs will be primary-ed on original primary cluster.
55 = Issue 'geopg takeover' on pgs so that they will be primary-ed on
60 = Issue 'geopg switchover' from <cluster-2> so that
geo_avs_rbac 43 Verify that a non-root user with "Geo Management" profile can
45 Verify that a role with "Geo Management" profile can do
54 Issue 'geopg switchover' from <cluster-1> so that
57 Issue 'geopg switchover' from <cluster-2> so that
66 Verify that a non-root user with "Geo Management" profile can
68 Verify that a role with "Geo Management" profile can do
77 Issue 'geopg switchover' from <cluster-1> so that
80 Issue 'geopg switchover' from <cluster-2> so that
89 Verify that a non-root user with no RBAC "Geo Management" profile
103 that PG will be primary-ed on original primary cluster
    [all...]
geo_avs 43 Verify that geopg switchover succeeds when AVS is in REP state.
49 = Issue 'geopg switchover' from <cluster-1> so that
52 = Issue 'geopg switchover' from <cluster-2> so that
61 Verify that 'geopg switchover' fails when AVS is in LOG state.
62 Verify that 'geopg switchover' success when AVS is in REP state,
74 replication rg online on that node.
77 = Issue 'geopg switchover' from <cluster-1> so that <cluster-2> will
81 = Issue 'geopg switchover' so that <cluster-2> will be the primary
89 Verify that geopg takeover succeeds when AVS is in REP state.
90 Verify that geopg switchover following a geopg takeover and reactivatin
    [all...]
  /test/ohacts/src/tset/sanity/doc/assertions/
transport 54 Verify that transport path is now faulted.
55 3. Verify that primary interconnect moved over.
57 5. Verify that client and server programs did not fail.
75 Verify that transport path is now faulted.
76 3. Verify that secondary interconnect moved over.
78 5. Verify that client and server programs did not fail.
scalable_reboot 52 = Send a client request and find out the node that serves the request.
54 = Make sure the node that was rebooted is completely up.
55 = Send client request again and make sure that the requests are being
72 = Send a client request and find out the node that serves the request.
73 = Reboot the node that is servicing the request.
74 = Make sure the node that was rebooted is completely up.
75 = Send client request again and make sure that the server node is same for
transport_reboot 43 If cluster node was rebooted the connection to that node should
44 be reset in one to three seconds and new connect request to that
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-mid/property/scf_simple_app_props_get/
ASSERTIONS 34 with a NULL instance name from a program that is not an smf
93 for an instance that has no service or instance properties
104 for an instance that has a default instance property group
115 for an instance that has a non-default instance property group
126 for an instance that has a default service property group
137 for an instance that has a non-default service property group
148 for an instance that has default and non-default
171 for an instance that has default and non-default
184 for an instance that has default and non-default
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-mid/property/scf_simple_app_props_get/
ASSERTIONS 34 with a NULL instance name from a program that is not an smf
93 for an instance that has no service or instance properties
104 for an instance that has a default instance property group
115 for an instance that has a non-default instance property group
126 for an instance that has a default service property group
137 for an instance that has a non-default service property group
148 for an instance that has default and non-default
171 for an instance that has default and non-default
184 for an instance that has default and non-default
  /test/ohacts/src/tset/geo/doc/
README 36 1st failover address that testsuite will use for 1st sndr set
41 2nd failover address that testsuite will use for 2nd sndr set
46 3rd failover address that testsuite will use for 1st HA-NFS
51 4th failover address that testsuite will use for 2nd HA-NFS
56 did of 1st available shared disk on primary cluster that testsuite
62 did of 2nd available shared disk on primary cluster that testsuite
73 1st failover address that testsuite will use for 1st sndr set
78 2nd failover address that testsuite will use for 2nd sndr set
83 3rd failover address that testsuite will use for 1st HA-NFS
88 4th failover address that testsuite will use for 2nd HA-NF
    [all...]
  /test/stcnv/usr/src/tools/diskomizer/
README 33 devices that are specified and then verifies the data that is read
34 back is the data that was written to that block. Every block of data
47 The source is lint and cstyle clean. Keep it that way.
55 that contains binaries for all the architecutures that diskomizer supports
58 2) The STC way which produces a package called SUNWstc-diskomizer that contains
100 You should always verify that diskomizer can detect and report data
102 EXPERT_O_EXCL=0 option to disomizer so that the device can be accessed
    [all...]
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/iterators/scf_iter_next_snapshot/
ASSERTIONS 37 2. Invoke scf_iter_next_snapshot(). Verify that the
66 5. Invoke scf_iter_next_snapshot(). Verify that the
95 4. Invoke scf_iter_next_snapshot(). Verify that the
123 4. Invoke scf_iter_next_snapshot(). Verify that the
126 5. Invoke scf_iter_next_snapshot() again. Verify that the
129 6. Invoke scf_iter_next_snapshot() a third time. Verify that
159 Verify that the call returned -1 and set the error code to
  /test/stcnv/usr/src/suites/os/lofi/
STATUS.LIST 29 This file lists tests that return a status other than 'PASS' for the
35 Some tests will return a status of 'UNTESTED', meaning that no attempt
55 named (non-global) zone, and in that case its only purpose is to
56 verify that the lofiadm command fails gracefull when executed in a
58 status of UNTESTED. Note that attempting to run any tests other than

Completed in 480 milliseconds

1 2 3 4 5 6 7 8 9