Skip to content

Commit b387201

Browse files
committed
Dev: behave: Add functional test case for previous commit
1 parent 3858c03 commit b387201

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

test/features/sbd_ui.feature

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,3 +132,21 @@ Feature: crm sbd ui test cases
132132
And Run "crm cluster restart --all" on "hanode1"
133133
Then Service "sbd.service" is "stopped" on "hanode1"
134134
Then Service "sbd.service" is "stopped" on "hanode2"
135+
136+
@clean
137+
Scenario: Leverage maintenance mode
138+
When Run "crm cluster init -y" on "hanode1"
139+
And Run "crm cluster join -c hanode1 -y" on "hanode2"
140+
Then Cluster service is "started" on "hanode1"
141+
Then Cluster service is "started" on "hanode2"
142+
When Run "crm configure primitive d Dummy" on "hanode1"
143+
When Try "crm cluster init sbd -s /dev/sda5 -y"
144+
Then Expected "Or use 'crm -F/--force' option to leverage maintenance mode" in stderr
145+
When Run "crm -F cluster init sbd -s /dev/sda5 -y" on "hanode1"
146+
Then Service "sbd" is "started" on "hanode1"
147+
And Service "sbd" is "started" on "hanode2"
148+
When Try "crm sbd purge"
149+
Then Expected "Or use 'crm -F/--force' option to leverage maintenance mode" in stderr
150+
When Run "crm -F sbd purge" on "hanode1"
151+
Then Service "sbd.service" is "stopped" on "hanode1"
152+
Then Service "sbd.service" is "stopped" on "hanode2"

0 commit comments

Comments
 (0)