diff --git a/test/run-functional-tests b/test/run-functional-tests index cd5558e466..0050db0670 100755 --- a/test/run-functional-tests +++ b/test/run-functional-tests @@ -1,5 +1,5 @@ #!/bin/bash -DOCKER_IMAGE=${DOCKER_IMAGE:-"liangxin1300/haleap:15.6"} +DOCKER_IMAGE=${DOCKER_IMAGE:-"liangxin1300/haleap:15.7"} PROJECT_PATH=$(dirname $(dirname `realpath $0`)) PROJECT_INSIDE="/opt/crmsh" DOCKER_SERVICE="docker.service" diff --git a/test/testcases/acl.exp b/test/testcases/acl.exp index fc8ca21989..4b20750c20 100644 --- a/test/testcases/acl.exp +++ b/test/testcases/acl.exp @@ -23,9 +23,6 @@ .INP: _test .INP: verify .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .INP: show node node1 primitive d0 ocf:pacemaker:Dummy \ diff --git a/test/testcases/bundle.exp b/test/testcases/bundle.exp index 97bab16eb9..b2bbc7bace 100644 --- a/test/testcases/bundle.exp +++ b/test/testcases/bundle.exp @@ -19,9 +19,6 @@ .INP: _test .INP: verify .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .INP: show node node1 \ attributes mem=16G diff --git a/test/testcases/confbasic.exp b/test/testcases/confbasic.exp index d870e8847b..b247340161 100644 --- a/test/testcases/confbasic.exp +++ b/test/testcases/confbasic.exp @@ -68,11 +68,12 @@ INFO: 37: "collocation" is accepted as "colocation" .INP: set d2.mondelay 45 .INP: _test .INP: verify +warning: Support for (such as in m) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +warning: Support for the Master role is deprecated and will be removed in a future release. Use Promoted instead. +Warnings found during check: config not valid WARNING: 53: c2: resource d1 is grouped, constraints should apply to the group .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .INP: show node node1 \ attributes mem=16G @@ -187,6 +188,10 @@ op_defaults opsdef2: \ rule 100: #uname eq node1 \ record-pending=true .INP: commit +warning: Support for (such as in m) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +warning: Support for the Master role is deprecated and will be removed in a future release. Use Promoted instead. +Warnings found during check: config not valid WARNING: 55: c2: resource d1 is grouped, constraints should apply to the group .TRY -F node maintenance node1 .TRY -F resource maintenance g1 off @@ -195,7 +200,8 @@ WARNING: 55: c2: resource d1 is grouped, constraints should apply to the group INFO: 'maintenance' attribute already exists in d1. Remove it? [YES] INFO: 'maintenance' attribute already exists in g1. Remove it? [YES] INFO: 'maintenance' attribute already exists in node1. Remove it? [YES] +warning: Support for (such as in m) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +warning: Support for the Master role is deprecated and will be removed in a future release. Use Promoted instead. +Warnings found during check: config not valid .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata diff --git a/test/testcases/edit.exp b/test/testcases/edit.exp index d76864031c..869362b3d0 100644 --- a/test/testcases/edit.exp +++ b/test/testcases/edit.exp @@ -196,12 +196,13 @@ rsc_defaults rsc_options: \ op_defaults op-options: \ timeout=60s .INP: commit +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +Warnings found during check: config not valid .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .INP: _test .INP: verify +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +Warnings found during check: config not valid .INP: primitive a0 ocf:heartbeat:Dummy .INP: primitive a1 ocf:heartbeat:Dummy .INP: primitive a2 ocf:heartbeat:Dummy @@ -215,11 +216,15 @@ op_defaults op-options: \ .INP: primitive aErr ocf:heartbeat:Dummy .INP: group as a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aErr .INP: commit +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +Warnings found during check: config not valid .INP: cd .. .INP: cd configure .INP: filter "sed '/as/s/a9//'" .INP: filter "sed '/as/s/a1/a1 a9/'" .INP: commit +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +Warnings found during check: config not valid .INP: cd .. .INP: cd configure .INP: filter "sed '/abs/s/a9//'" @@ -331,6 +336,8 @@ INFO: 89: apparently there is nothing to commit INFO: 89: try changing something first .INP: _test .INP: verify +warning: Support for multiple rule elements in a location constraint is deprecated and will be removed in a future release (use a single new rule combining the previous rules with boolean-op set to 'or' instead) +Warnings found during check: config not valid .INP: show node node1 \ attributes mem=16G diff --git a/test/testcases/file.exp b/test/testcases/file.exp index e0a733eeb2..3b648cb91a 100644 --- a/test/testcases/file.exp +++ b/test/testcases/file.exp @@ -46,9 +46,6 @@ op_defaults op-options: \ .INP: load update sample.txt ERROR: 4: syntax: Unknown command near parsing 'op stop timeout=20s interval=0s' .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .TRY configure show node node1 primitive p0 ocf:pacemaker:Dummy \ diff --git a/test/testcases/newfeatures.exp b/test/testcases/newfeatures.exp index 8a8e205341..c3631ef0ac 100644 --- a/test/testcases/newfeatures.exp +++ b/test/testcases/newfeatures.exp @@ -76,7 +76,4 @@ alert notify_9 "/usr/share/pacemaker/alerts/alert_snmp.sh" \ .INP: _test .INP: verify .EXT crm_attribute --list-options=cluster --all --output-as=xml -.EXT crmd metadata -.EXT pengine metadata -.EXT cib metadata .INP: commit diff --git a/test/testcases/ra.exp b/test/testcases/ra.exp index e94dcf5f01..d0edab70a1 100644 --- a/test/testcases/ra.exp +++ b/test/testcases/ra.exp @@ -68,83 +68,84 @@ livedangerously (enum): Live Dangerously!! Viva la Vida Loca! pcmk_action_limit (integer, [1]): The maximum number of actions can be performed in parallel on this device - Cluster property concurrent-fencing=true needs to be configured first.Then use this to specify the maximum number of actions can be performed in parallel on this device. -1 is unlimited. + Cluster property concurrent-fencing="true" needs to be configured first. Then use this to specify the maximum number of actions can be performed in parallel on this device. A value of -1 means an unlimited number of actions can be performed in parallel. pcmk_delay_base (string, [0s]): Enable a base delay for fencing actions and specify base delay value. - This enables a static delay for fencing actions, which can help avoid "death matches" where two nodes try to fence each other at the same time. If pcmk_delay_max is also used, a random delay will be added such that the total delay is kept below that value.This can be set to a single time value to apply to any node targeted by this device (useful if a separate device is configured for each target), or to a node map (for example, "node1:1s;node2:5") to set a different value per target. + This enables a static delay for fencing actions, which can help avoid "death matches" where two nodes try to fence each other at the same time. If pcmk_delay_max is also used, a random delay will be added such that the total delay is kept below that value. This can be set to a single time value to apply to any node targeted by this device (useful if a separate device is configured for each target), or to a node map (for example, "node1:1s;node2:5") to set a different value for each target. pcmk_delay_max (time, [0s]): Enable a delay of no more than the time specified before executing fencing actions. Enable a delay of no more than the time specified before executing fencing actions. Pacemaker derives the overall delay by taking the value of pcmk_delay_base and adding a random delay value such that the sum is kept below this maximum. -pcmk_host_argument (string, [port]): Advanced use only: An alternate parameter to supply instead of 'port' - some devices do not support the standard 'port' parameter or may provide additional ones. Use this to specify an alternate, device-specific, parameter that should indicate the machine to be fenced. A value of none can be used to tell the cluster not to supply any additional parameters. +pcmk_host_argument (string, [port]): *** Advanced Use Only *** An alternate parameter to supply instead of 'port' + Some devices do not support the standard 'port' parameter or may provide additional ones. Use this to specify an alternate, device-specific, parameter that should indicate the machine to be fenced. A value of "none" can be used to tell the cluster not to supply any additional parameters. -pcmk_host_check (string, [dynamic-list]): How to determine which machines are controlled by the device. - Allowed values: dynamic-list (query the device via the 'list' command), static-list (check the pcmk_host_list attribute), status (query the device via the 'status' command), none (assume every device can fence every machine) +pcmk_host_check (select): How to determine which nodes can be targeted by the device + Use "dynamic-list" to query the device via the 'list' command; "static-list" to check the pcmk_host_list attribute; "status" to query the device via the 'status' command; or "none" to assume every device can fence every node. The default value is "static-list" if pcmk_host_map or pcmk_host_list is set; otherwise "dynamic-list" if the device supports the list operation; otherwise "status" if the device supports the status operation; otherwise "none" Allowed values: dynamic-list, static-list, status, none + Allowed values: dynamic-list, static-list, status, none -pcmk_host_list (string): Eg. node1,node2,node3 - A list of machines controlled by this device (Optional unless pcmk_host_list=static-list) +pcmk_host_list (string): Nodes targeted by this device + Comma-separated list of nodes that can be targeted by this device (for example, "node1,node2,node3"). If pcmk_host_check is "static-list", either this or pcmk_host_map must be set. -pcmk_host_map (string): A mapping of host names to ports numbers for devices that do not support host names. - Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for node1 and ports 2 and 3 for node2 +pcmk_host_map (string): A mapping of node names to port numbers for devices that do not support node names. + For example, "node1:1;node2:2,3" would tell the cluster to use port 1 for node1 and ports 2 and 3 for node2. -pcmk_list_action (string, [list]): Advanced use only: An alternate command to run instead of 'list' +pcmk_list_action (string, [list]): *** Advanced Use Only *** An alternate command to run instead of 'list' Some devices do not support the standard commands or may provide additional ones.Use this to specify an alternate, device-specific, command that implements the 'list' action. -pcmk_list_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'list' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'list' actions before giving up. +pcmk_list_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'list' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'list' action before giving up. -pcmk_list_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for list actions instead of stonith-timeout +pcmk_list_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'list' actions instead of stonith-timeout Some devices need much more/less time to complete than normal.Use this to specify an alternate, device-specific, timeout for 'list' actions. -pcmk_monitor_action (string, [monitor]): Advanced use only: An alternate command to run instead of 'monitor' +pcmk_monitor_action (string, [monitor]): *** Advanced Use Only *** An alternate command to run instead of 'monitor' Some devices do not support the standard commands or may provide additional ones.Use this to specify an alternate, device-specific, command that implements the 'monitor' action. -pcmk_monitor_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'monitor' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'monitor' actions before giving up. +pcmk_monitor_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'monitor' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'monitor' action before giving up. -pcmk_monitor_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for monitor actions instead of stonith-timeout - Some devices need much more/less time to complete than normal.\nUse this to specify an alternate, device-specific, timeout for 'monitor' actions. +pcmk_monitor_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'monitor' actions instead of stonith-timeout + Some devices need much more/less time to complete than normal. Use this to specify an alternate, device-specific, timeout for 'monitor' actions. -pcmk_off_action (string, [off]): Advanced use only: An alternate command to run instead of 'off' +pcmk_off_action (string, [off]): *** Advanced Use Only *** An alternate command to run instead of 'off' Some devices do not support the standard commands or may provide additional ones.Use this to specify an alternate, device-specific, command that implements the 'off' action. -pcmk_off_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'off' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'off' actions before giving up. +pcmk_off_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'off' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'off' action before giving up. -pcmk_off_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for off actions instead of stonith-timeout +pcmk_off_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'off' actions instead of stonith-timeout Some devices need much more/less time to complete than normal.Use this to specify an alternate, device-specific, timeout for 'off' actions. -pcmk_on_action (string, [on]): Advanced use only: An alternate command to run instead of 'on' +pcmk_on_action (string, [on]): *** Advanced Use Only *** An alternate command to run instead of 'on' Some devices do not support the standard commands or may provide additional ones.Use this to specify an alternate, device-specific, command that implements the 'on' action. -pcmk_on_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'on' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'on' actions before giving up. +pcmk_on_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'on' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'on' action before giving up. -pcmk_on_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for on actions instead of stonith-timeout +pcmk_on_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'on' actions instead of stonith-timeout Some devices need much more/less time to complete than normal.Use this to specify an alternate, device-specific, timeout for 'on' actions. -pcmk_reboot_action (string, [reboot]): Advanced use only: An alternate command to run instead of 'reboot' - Some devices do not support the standard commands or may provide additional ones.\nUse this to specify an alternate, device-specific, command that implements the 'reboot' action. +pcmk_reboot_action (string, [reboot]): *** Advanced Use Only *** An alternate command to run instead of 'reboot' + Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'reboot' action. -pcmk_reboot_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'reboot' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'reboot' actions before giving up. +pcmk_reboot_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'reboot' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'reboot' action before giving up. -pcmk_reboot_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for reboot actions instead of stonith-timeout +pcmk_reboot_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'reboot' actions instead of stonith-timeout Some devices need much more/less time to complete than normal.Use this to specify an alternate, device-specific, timeout for 'reboot' actions. -pcmk_status_action (string, [status]): Advanced use only: An alternate command to run instead of 'status' +pcmk_status_action (string, [status]): *** Advanced Use Only *** An alternate command to run instead of 'status' Some devices do not support the standard commands or may provide additional ones.Use this to specify an alternate, device-specific, command that implements the 'status' action. -pcmk_status_retries (integer, [2]): Advanced use only: The maximum number of times to retry the 'status' command within the timeout period - Some devices do not support multiple connections. Operations may 'fail' if the device is busy with another task so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries 'status' actions before giving up. +pcmk_status_retries (integer, [2]): *** Advanced Use Only *** The maximum number of times to try the 'status' command within the timeout period + Some devices do not support multiple connections. Operations may "fail" if the device is busy with another task. In that case, Pacemaker will automatically retry the operation if there is time remaining. Use this option to alter the number of times Pacemaker tries a 'status' action before giving up. -pcmk_status_timeout (time, [60s]): Advanced use only: Specify an alternate timeout to use for status actions instead of stonith-timeout +pcmk_status_timeout (time, [60s]): *** Advanced Use Only *** Specify an alternate timeout to use for 'status' actions instead of stonith-timeout Some devices need much more/less time to complete than normal.Use this to specify an alternate, device-specific, timeout for 'status' actions. ## Operations' defaults (advisory minimum): start timeout=20s - stop timeout=15 + stop timeout=15s status timeout=20s - monitor timeout=20s interval=3600 + monitor timeout=20s interval=3600s diff --git a/test/testcases/resource.exp b/test/testcases/resource.exp index afdd7184ca..01aeb9690b 100644 --- a/test/testcases/resource.exp +++ b/test/testcases/resource.exp @@ -1148,48 +1148,62 @@ WARNING: This command 'rm' is deprecated, please use 'delete' INFO: "rm" is accepted as "delete" .TRY configure ms msg g WARNING: The "ms" command is deprecated, please use: clone msg g meta promotable=true +warning: Support for (such as in msg) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +Warnings found during check: config not valid .TRY resource scores .EXT crm_simulate -sUL 2 of 6 resource instances DISABLED and 0 BLOCKED from further action due to failure -Node node1: UNCLEAN (offline) +Current cluster status: + * Node List: + * Node node1: UNCLEAN (offline) - st (stonith:null): Stopped - Stopped: [ node1 ] - Stopped: [ node1 ] - p3 (ocf::heartbeat:Dummy): Stopped ( disabled ) - Stopped: [ node1 ] + * Full List of Resources: + * st (stonith:null): Stopped + * Clone Set: c1 [p1] (unmanaged): + * Stopped: [ node1 ] + * Clone Set: m1 [p2] (promotable): + * Stopped: [ node1 ] + * p3 (ocf::heartbeat:Dummy): Stopped (disabled) + * Clone Set: msg [g] (promotable): + * Stopped: [ node1 ] -Original: node1 capacity: -pcmk__primitive_assign: st allocation score on node1: 0 -pcmk__clone_assign: c1 allocation score on node1: 0 -pcmk__clone_assign: p1:0 allocation score on node1: 0 -pcmk__primitive_assign: p1:0 allocation score on node1: -INFINITY -pcmk__clone_assign: m1 allocation score on node1: 0 -pcmk__clone_assign: p2:0 allocation score on node1: 0 -pcmk__primitive_assign: p2:0 allocation score on node1: -INFINITY -p2:0 promotion score on none: 0 -pcmk__primitive_assign: p3 allocation score on node1: -INFINITY -pcmk__clone_assign: msg allocation score on node1: 0 -pcmk__clone_assign: g:0 allocation score on node1: 0 -pcmk__clone_assign: p0:0 allocation score on node1: 0 -pcmk__clone_assign: p4:0 allocation score on node1: 0 -pcmk__group_assign: g:0 allocation score on node1: -INFINITY -pcmk__group_assign: p0:0 allocation score on node1: -INFINITY -pcmk__group_assign: p4:0 allocation score on node1: -INFINITY -pcmk__primitive_assign: p0:0 allocation score on node1: -INFINITY -pcmk__primitive_assign: p4:0 allocation score on node1: -INFINITY -g:0 promotion score on none: 0 -Remaining: node1 capacity: +Assignment Scores and Utilization Information: + * Original: node1 capacity: + * pcmk__primitive_assign: st allocation score on node1: 0 + * pcmk__clone_assign: c1 allocation score on node1: 0 + * pcmk__clone_assign: p1:0 allocation score on node1: 0 + * pcmk__primitive_assign: p1:0 allocation score on node1: -INFINITY + * pcmk__clone_assign: m1 allocation score on node1: 0 + * pcmk__clone_assign: p2:0 allocation score on node1: 0 + * pcmk__primitive_assign: p2:0 allocation score on node1: -INFINITY + * p2:0 promotion score (inactive): -INFINITY + * pcmk__primitive_assign: p3 allocation score on node1: -INFINITY + * pcmk__clone_assign: msg allocation score on node1: 0 + * pcmk__clone_assign: g:0 allocation score on node1: 0 + * pcmk__clone_assign: p0:0 allocation score on node1: 0 + * pcmk__clone_assign: p4:0 allocation score on node1: 0 + * pcmk__group_assign: g:0 allocation score on node1: -INFINITY + * pcmk__group_assign: p0:0 allocation score on node1: -INFINITY + * pcmk__group_assign: p4:0 allocation score on node1: -INFINITY + * pcmk__primitive_assign: p0:0 allocation score on node1: -INFINITY + * pcmk__primitive_assign: p4:0 allocation score on node1: -INFINITY + * g:0 promotion score (inactive): -INFINITY + * Remaining: node1 capacity: +Transition Summary: .SETENV showobj= .TRY configure primitive p5 Dummy .EXT crm_resource --show-metadata ocf:heartbeat:Dummy +warning: Support for (such as in msg) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +Warnings found during check: config not valid .EXT crm_resource --show-metadata stonith:null .EXT stonithd metadata .EXT crm_resource --show-metadata ocf:pacemaker:Dummy .EXT crm_resource --show-metadata ocf:heartbeat:Delay .TRY configure group g1 p5 +warning: Support for (such as in msg) is deprecated and will be removed in a future release. Use with a promotable meta-attribute instead. +Warnings found during check: config not valid .TRY resource manage p5 .SETENV showobj=p5 .TRY -F resource maintenance p5 on diff --git a/test_container/Dockerfile b/test_container/Dockerfile index 6488cae915..6115a0643f 100644 --- a/test_container/Dockerfile +++ b/test_container/Dockerfile @@ -9,6 +9,10 @@ RUN zypper refresh && \ python3 python3-pip python3-lxml python3-python-dateutil python3-setuptools python3-PyYAML python3-curses python3-behave \ csync2 libglue-devel corosync corosync-qdevice pacemaker pacemaker-remote booth corosync-qnetd +RUN zypper ar -f -G https://download.opensuse.org/repositories/home:/yan_gao:/branches:/network:/ha-clustering:/Factory:/2.1/openSUSE_Leap_15.6/ repo_update_pacemaker +RUN zypper --non-interactive refresh +RUN zypper --non-interactive up --allow-vendor-change -y pacemaker + RUN ssh-keygen -t rsa -f /root/.ssh/id_rsa -N '' && \ cp /root/.ssh/id_rsa.pub /root/.ssh/authorized_keys && \ chmod 0600 /root/.ssh/authorized_keys