Bug 960987 - [RFE] : Handling exit status of the commands execution from all the nodes
[RFE] : Handling exit status of the commands execution from all the nodes
Product: Beaker
Classification: Community
Component: tests (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
Depends On:
  Show dependency treegraph
Reported: 2013-05-08 09:11 EDT by spandura
Modified: 2018-02-05 19:41 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-08 20:37:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description spandura 2013-05-08 09:11:46 EDT
Description of problem:
In a multi-node testing environment we have to fail a test case when 
certain commands on any one of the node fails . For example : if 
mounting fails on client node , that test case execution should not be 
continued. A message to be sent to all other machines i.e 
masternode/node/peer in this case to stop the execution.

*This is the basic requirement for multi-node testing.* We want to check the exit status after every step. For example in most of our testcases the set-up includes :

1) peer probing
2) volume_create
3) volume_info
4) volume_start
5) volume_status
6) mount

In every step we should check the exit status from all the nodes and if 
any one node has non-zero exit status we should stop that test case and 
move on to next test case in that task.
Comment 1 Nick Coghlan 2013-05-08 20:37:51 EDT
From Beaker's point of view, we don't have the ability to tell the test harness to abandon a single task - we can only abort the remainder of the recipe.

We also have no plans to add that capability to the default test harness (beah).

However, what we have added in Beaker 0.12 is support for using a harness other than the default (see http://beaker-project.org/docs/alternative-harnesses/).

Our initial focus in on getting autotest up and running as a fully supported alternative client, so if this capability is to be provided, it would be through autotest rather than through beah.

The relevant autotest issue for the integration is here: https://github.com/autotest/autotest/issues/609
Latest pull request: https://github.com/autotest/autotest/pull/629

Note You need to log in before you can comment on or make changes to this bug.