Dev: behave: Adjust functional test for previous changes

Author: liangxin1300

test/features/bootstrap_bugs.feature

@@ -4,6 +4,31 @@ Feature: Regression test for bootstrap bugs
   Tag @clean means need to stop cluster service if the service is available
   Need nodes: hanode1 hanode2 hanode3
 
+  @clean
+  Scenario: Stages dependency (bsc#1175865)
+    Given   Cluster service is "stopped" on "hanode1"
+    And     Cluster service is "stopped" on "hanode2"
+    When    Try "crm cluster init cluster -y" on "hanode1"
+    Then    Except "ERROR: cluster.init: Please run 'ssh' stage first"
+    When    Run "crm cluster init ssh -y" on "hanode1"
+    When    Try "crm cluster init cluster -y" on "hanode1"
+    Then    Except "ERROR: cluster.init: Please run 'csync2' stage first"
+    When    Run "crm cluster init csync2 -y" on "hanode1"
+    When    Try "crm cluster init cluster -y" on "hanode1"
+    Then    Except "ERROR: cluster.init: Please run 'corosync' stage first"
+    When    Run "crm cluster init corosync -y" on "hanode1"
+    When    Run "crm cluster init cluster -y" on "hanode1"
+    Then    Cluster service is "started" on "hanode1"
+
+    When    Try "crm cluster join cluster -c hanode1 -y" on "hanode2"
+    Then    Except "ERROR: cluster.join: Please run 'ssh' stage first"
+    When    Try "crm cluster join ssh -c hanode1 -y" on "hanode2"
+    When    Try "crm cluster join cluster -c hanode1 -y" on "hanode2"
+    Then    Except "ERROR: cluster.join: Please run 'csync2' stage first"
+    When    Try "crm cluster join csync2 -c hanode1 -y" on "hanode2"
+    When    Try "crm cluster join cluster -c hanode1 -y" on "hanode2"
+    Then    Cluster service is "started" on "hanode2"
+
   @clean
   Scenario: Set placement-strategy value as "default"(bsc#1129462)
     Given   Cluster service is "stopped" on "hanode1"

test/features/bootstrap_options.feature

@@ -36,6 +36,15 @@ Feature: crmsh bootstrap process - options
     When    Try "crm cluster init sbd -N hanode1 -N hanode2 -y" on "hanode1"
     Then    Expected "Can't use -N/--nodes option and stage(sbd) together" in stderr
 
+  @clean
+  Scenario: Stage validation
+    When    Try "crm cluster init fdsf -y" on "hanode1"
+    Then    Expected "Invalid stage: fdsf(available stages: ssh, csync2, corosync, sbd, cluster, ocfs2, admin, qdevice)" in stderr
+    When    Try "crm cluster join fdsf -y" on "hanode1"
+    Then    Expected "Invalid stage: fdsf(available stages: ssh, csync2, ssh_merge, cluster)" in stderr
+    When    Try "crm cluster join ssh -y" on "hanode1"
+    Then    Expected "Can't use stage(ssh) without specifying cluster node" in stderr
+
   @clean
   Scenario: Init whole cluster service on node "hanode1" using "--node" option
     Given   Cluster service is "stopped" on "hanode1"
@@ -46,6 +55,9 @@ Feature: crmsh bootstrap process - options
     And     Online nodes are "hanode1 hanode2"
     And     Show cluster status on "hanode1"
 
+    When    Try "crm cluster init cluster -y" on "hanode1"
+    Then    Expected "Cluster is active, can't run 'cluster' stage" in stderr
+
   @clean
   Scenario: Bind specific network interface using "-i" option
     Given   Cluster service is "stopped" on "hanode1"
@@ -89,6 +101,9 @@ Feature: crmsh bootstrap process - options
     And     IP "@hanode2.ip.default" is used by corosync on "hanode2"
     And     IP "@hanode2.ip.0" is used by corosync on "hanode2"
 
+    When    Try "crm cluster join cluster -c hanode1 -y" on "hanode2"
+    Then    Expected "Cluster is active, can't run 'cluster' stage" in stderr
+
   @clean
   Scenario: Using "-i" option with IP address
     Given   Cluster service is "stopped" on "hanode1"

test/features/qdevice_validate.feature

@@ -110,7 +110,7 @@ Feature: corosync qdevice/qnetd options validate
   Scenario: Run qdevice stage on inactive cluster node
     Given   Cluster service is "stopped" on "hanode1"
     When    Try "crm cluster init qdevice --qnetd-hostname=qnetd-node"
-    Then    Except "ERROR: cluster.init: Cluster is inactive - can't run qdevice stage"
+    Then    Except "ERROR: cluster.init: Cluster is inactive, can't run 'qdevice' stage"
 
   @clean
   Scenario: Run qdevice stage but miss "--qnetd-hostname" option