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
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
@cluster_api
Feature: Functional test to cover SAP clusterAPI
To avoid possible regression on crmsh side when adapting SAP Applications
Tag @clean means need to stop cluster service if the service is available
Need nodes: hanode1 hanode2
Background: Setup a two nodes cluster
Given Cluster service is "stopped" on "hanode1"
And Cluster service is "stopped" on "hanode2"
When Run "crm cluster init -y" on "hanode1"
Then Cluster service is "started" on "hanode1"
And Show cluster status on "hanode1"
When Run "crm cluster join -c hanode1 -y" on "hanode2"
Then Cluster service is "started" on "hanode2"
And Online nodes are "hanode1 hanode2"
When Run "crm configure primitive d Dummy" on "hanode1"
And Wait "3" seconds
Then Resource "d" type "Dummy" is "Started"
And Show cluster status on "hanode1"
When Run "echo 'export PATH=$PATH:/usr/sbin/' > ~hacluster/.bashrc" on "hanode1"
When Run "echo 'export PATH=$PATH:/usr/sbin/' > ~hacluster/.bashrc" on "hanode2"
@clean
Scenario: Start and stop resource by hacluster
When Run "su - hacluster -c 'crm resource stop d'" on "hanode1"
Then Expected return code is "0"
When Wait "3" seconds
Then Resource "d" type "Dummy" is "Stopped"
And Show cluster status on "hanode1"
When Run "su - hacluster -c 'crm resource start d'" on "hanode1"
Then Expected return code is "0"
When Wait "3" seconds
Then Resource "d" type "Dummy" is "Started"
And Show cluster status on "hanode1"
@clean
Scenario: Resource move by hacluster
Given Resource "d" is started on "hanode1"
# move <res> <node>
When Run "su - hacluster -c 'crm resource move d hanode2'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode2"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
# move <res> <node> force
When Run "su - hacluster -c 'crm resource move d hanode1'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode1"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
# move <res> force
When Run "su - hacluster -c 'crm resource move d force'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode2"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
# move <res> <lifetime> force
When Run "su - hacluster -c 'crm resource move d PT5M force'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode1"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
# move <res> <node> <lifetime>
When Run "su - hacluster -c 'crm resource move d hanode2 PT5M'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode2"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
# move <res> <node> <lifetime> force
When Run "su - hacluster -c 'crm resource move d hanode1 PT5M force'" on "hanode1"
Then Expected return code is "0"
When Run "sleep 2" on "hanode1"
Then Resource "d" is started on "hanode1"
When Run "su - hacluster -c 'crm resource clear d'" on "hanode1"
Then Expected return code is "0"
When Try "crm resource move d hanode2 PT5M force xxx"
Then Except "ERROR: resource.move: usage: move <rsc> [<node>] [<lifetime>] [force]"
When Try "crm resource move d hanode2 PT5M forcd"
Then Except "ERROR: resource.move: usage: move <rsc> [<node>] [<lifetime>] [force]"
When Try "crm resource move d xxxx PT5M force"
Then Except "ERROR: resource.move: Not our node: xxxx"
When Try "crm resource move d"
Then Except "ERROR: resource.move: No target node: Move requires either a target node or 'force'"
@clean
Scenario: Run "crm configure show" by hacluster
When Run "crm configure primitive d2 Dummy op monitor interval=10s timeout=20s on-fail=restart params fake=test meta resource-stickiness=5000" on "hanode1"
And Run "crm configure group g d2 meta resource-stickiness=3000" on "hanode1"
And Wait "3" seconds
Then Resource "d2" type "Dummy" is "Started"
And Show cluster status on "hanode1"
When Run "su - hacluster -c 'crm configure show'" on "hanode1"
Then Expected return code is "0"
@clean
Scenario: pacemaker ACL related operations by hacluster
When Run "su - hacluster -c 'crm configure primitive d2 Dummy'" on "hanode1"
And Wait "3" seconds
Then Resource "d2" type "Dummy" is "Started"
When Run "su - hacluster -c 'crm maintenance on'" on "hanode1"
When Run "crm_mon -1" on "hanode1"
Then Expected "Resource management is DISABLED" in stdout
When Run "su - hacluster -c 'crm maintenance off'" on "hanode1"
When Run "crm_mon -1" on "hanode1"
Then Expected "Resource management is DISABLED" not in stdout
When Run "su - hacluster -c 'crm node standby hanode2'" on "hanode1"
Then Node "hanode2" is standby
When Run "su - hacluster -c 'crm node online hanode2'" on "hanode1"
Then Node "hanode2" is online
When Run "su - hacluster -c 'crm ra providers Dummy'" on "hanode1"
Then Expected "heartbeat pacemaker" in stdout
When Run "su - hacluster -c 'crm status'" on "hanode1"
Then Expected "Online: [ hanode1 hanode2 ]" in stdout
When Run "su - hacluster -c '/usr/sbin/crm report /tmp/report'" on "hanode1"
Then No crmsh tracebacks
Then File "/tmp/report.tar.bz2" exists on "hanode1"
And Directory "hanode1" in "/tmp/report.tar.bz2"
And Directory "hanode2" in "/tmp/report.tar.bz2"
And File "pacemaker.log" in "/tmp/report.tar.bz2"
And File "corosync.conf" in "/tmp/report.tar.bz2"
@clean
Scenario: crm configure verify return code
When Run "crm configure verify" on "hanode1"
Then Expected return code is "0"
When Try "crm -F configure property stonith-enabled=true"
Then Expected return code is "0"
When Try "crm configure verify"
Then Expected return code is "1"
Then Expected "Configuration invalid (with errors)" in stdout
When Run "crm configure property stonith-enabled=false" on "hanode1"
Then Expected return code is "0"
When Run "crm -F configure primitive d-require-fence Dummy meta requires=fencing" on "hanode1"
When Try "crm configure verify"
Then Expected return code is "1"
Then Expected "Configuration invalid (with warnings)" in stdout
When Try "crm -F configure primitive d-unknown-param Dummy params xxx=xxx"
When Try "crm configure verify"
Then Expected return code is "1"
Then Expected "parameter "xxx" is not known" in stderr
@clean
Scenario: crm cluster start should return 0 for successful repeated execution (bsc#1241358)
When Run "crm cluster start" on "hanode1"
Then Expected return code is "0"
Then Expected "The cluster stack already started on hanode1" in stdout
When Run "crm cluster stop" on "hanode1"
And Run "crm cluster stop" on "hanode1"
Then Expected return code is "0"
Then Expected "The cluster stack already stopped on hanode1" in stdout
|
