Bug 730971 - Harness does not like rebooting while event is processed in a loop
Summary: Harness does not like rebooting while event is processed in a loop
Keywords:
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: beah
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: SimpleHarness
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-16 12:39 UTC by Marian Csontos
Modified: 2018-11-09 23:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Marian Csontos 2011-08-16 12:39:53 UTC
Description of problem:

Try running following task:

<task name="/distribution/command" role="STANDALONE">
	<params>
		<param name="CMDS_TO_RUN" value="reboot"/>
	</params>
</task>

It can cause EWD in next task.


Version-Release number of selected component (if applicable):
0.6.17

How reproducible:
?

Steps to Reproduce:
1. run a recipe with given task
  
Actual results:
EWD in next task when we loose start event.

Expected results:
No EWD

Additional info:

Using plain reboot is not a good idea: next task started to be processed and machine is rebooted at a random moment during task exec which itself is enough to break some tests for example any test with rhts-reboot and $REBOOTCOUNT.

Also, harness did not handle the situation gracefully: network is down and an event is processed in a cycle. When reboot caught it the event was not requeued. Unfortunately it was start event, which is important in the event flow.

Comment 1 Nick Coghlan 2012-10-17 04:37:56 UTC
Bulk reassignment of issues as Bill has moved to another team.


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