1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
@resource
Feature: Use "crm resource failcount" to manage failcounts
Tag @clean means need to stop cluster service if the service is available
Need nodes: hanode1
Background: Setup one node cluster and configure a Dummy resource
Given Cluster service is "stopped" on "hanode1"
When Run "crm cluster init -y" on "hanode1"
Then Cluster service is "started" on "hanode1"
When Run "crm configure primitive d Dummy op monitor interval=3s" on "hanode1"
Then Resource "d" type "Dummy" is "Started"
@clean
Scenario: Validation, input the wrong parameters
When Try "crm resource failcount ddd show hanode1"
Then Except "Resource ddd not in this cluster"
When Try "crm resource failcount d showss hanode1"
Then Except "ERROR: resource.failcount: showss is not valid command(should be one of delete, set, show)"
When Try "crm resource failcount d set hanode11 0"
Then Except "ERROR: resource.failcount: Node hanode11 not in this cluster"
When Try "crm resource failcount d set hanode1 12s"
Then Except "ERROR: resource.failcount: value should be a non-negative integer or 'INFINITY'"
@clean
Scenario: Set the failcount to 0
When Run "rm -f /run/resource-agents/Dummy-d.state" on "hanode1"
And Wait "5" seconds
Then Resource "d" failcount on "hanode1" is "1"
When Try "crm resource failcount d set hanode1 0 start 0"
Then Except "ERROR: resource.failcount: Should specify operation between (monitor)"
When Try "crm resource failcount d set hanode1 0 monitor 5"
Then Except "ERROR: resource.failcount: Should specify (operation, interval) between [('monitor', '3')]"
When Run "crm resource failcount d set hanode1 0" on "hanode1"
Then Resource "d" failcount on "hanode1" is "0"
# no failcount entry
When Run "crm configure primitive d2 Dummy op monitor interval=10s" on "hanode1"
Then Resource "d2" type "Dummy" is "Started"
When Try "crm resource failcount d2 set hanode1 0"
Then Except "WARNING: Should specify operation and interval"
When Run "crm resource failcount d2 set hanode1 0 monitor 10" on "hanode1"
Then Resource "d2" failcount on "hanode1" is "0"
@clean
Scenario: Set multiple failcounts to 0
When Run "sed -i -e '/rm \${OCF_RESKEY_state}/a\' -e "else\nreturn \$OCF_ERR_GENERIC" /usr/lib/ocf/resource.d/heartbeat/Dummy" on "hanode1"
And Run "rm -f /run/resource-agents/Dummy-d.state" on "hanode1"
And Wait "5" seconds
Then Resource "d" failcount on "hanode1" is "INFINITY"
"""
now have two failcount entries, one is monitor, another is stop
"""
When Run "crm resource failcount d set hanode1 100 stop 0" on "hanode1"
"""
set stop failcounts to 100, specify both operation and interval
"""
Then Resource "d" failcount on "hanode1" is "101"
When Run "crm resource failcount d set hanode1 0" on "hanode1"
"""
set all failcounts to 0
"""
Then Resource "d" failcount on "hanode1" is "0"
When Run "crm resource cleanup" on "hanode1"
And Wait "5" seconds
And Run "rm -f /run/resource-agents/Dummy-d.state" on "hanode1"
And Wait "5" seconds
Then Resource "d" failcount on "hanode1" is "INFINITY"
"""
now have two failcount entries, one is monitor, another is stop
"""
When Run "crm resource failcount d set hanode1 0 stop" on "hanode1"
"""
set stop failcounts to 0
"""
Then Resource "d" failcount on "hanode1" is "1"
When Run "crm resource failcount d set hanode1 0 monitor" on "hanode1"
"""
set monitor failcounts to 0
"""
Then Resource "d" failcount on "hanode1" is "0"
When Try "crm resource failcount d set hanode1 1"
Then Except "ERROR: resource.failcount: Should specify (operation, interval) between [('monitor', '3'), ('stop', '0')]"
When Run "crm resource failcount d set hanode1 1 stop" on "hanode1"
Then Resource "d" failcount on "hanode1" is "1"
|
