Skip to content

Commit 3c74835

Browse files
committed
Dev: behave: Adjust functional test for previous commit
1 parent fe09cba commit 3c74835

File tree

2 files changed

+11
-0
lines changed

2 files changed

+11
-0
lines changed

test/features/bootstrap_sbd_delay.feature

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,9 @@ Feature: configure sbd delay start correctly
9797
And SBD option "SBD_WATCHDOG_TIMEOUT" value is "15"
9898
And Cluster property "stonith-timeout" is "71"
9999

100+
When Try "crm configure property stonith-watchdog-timeout=1" on "hanode1"
101+
Then Except "Can't set stonith-watchdog-timeout to 1 because it is less than SBD_WATCHDOG_TIMEOUT(now: 15)" in stderr
102+
100103
@clean
101104
Scenario: disk-based SBD with big sbd_watchdog_timeout
102105
When Run "sed -i 's/watchdog_timeout: 15/watchdog_timeout: 60/' /etc/crm/profiles.yml" on "hanode1"

test/features/configure_bugs.feature

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,3 +81,11 @@ Feature: Functional test for configure sub level
8181
Then Cluster service is "started" on "hanode1"
8282
When Run "crm node attribute hanode1 set cpu 2" on "hanode1"
8383
Then Run "crm -F configure filter "sed 's/cpu=/#cpu='/g"" OK on "hanode1"
84+
85+
@clean
86+
Scenario: Set stonith-watchdog-timeout when sbd.service is disactive
87+
Given Cluster service is "stopped" on "hanode1"
88+
When Run "crm cluster init -y" on "hanode1"
89+
Then Cluster service is "started" on "hanode1"
90+
When Try "crm configure property stonith-watchdog-timeout=20" on "hanode1"
91+
Then Except "Can't set stonith-watchdog-timeout because sbd.service is not active" in stderr

0 commit comments

Comments
 (0)