Bug 1083648 - beaker-provision unnecessarily enforces quiescent period in between netboot commands and power commands
Summary: beaker-provision unnecessarily enforces quiescent period in between netboot c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 23.3
Assignee: Dan Callaghan
QA Contact: Dan Callaghan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-02 15:56 UTC by Bill Peck
Modified: 2018-02-06 00:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 06:44:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Bill Peck 2014-04-02 15:56:11 UTC
Description of problem:

Some systems require a long sleep between off and on power states (180 seconds).  Unfortunately dealing with the netboot entries (clearing, setting) are considered like power commands.  This causes unnecessary delays when provisioning a system where the off command is delayed and then the on command is delayed.

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

How reproducible:
everytime

Steps to Reproduce:
1. configure a system with a long Quiescent period
2. provision a job
3. observe

Actual results:
off command will be delayed because of the netboot setup

Expected results:
off command doesn't need to be delayed in this situation.

Comment 2 Dan Callaghan 2014-04-03 01:36:38 UTC
I'm pretty sure we don't enforce any delays before configure_netboot, clear_netboot, and clear_logs.

I think the problem is that Beaker enforces the delay before 'off' based on when the last command of any sort ran. It should be based on when the last power command ran instead.

Comment 3 Dan Callaghan 2016-10-20 07:02:27 UTC
http://gerrit.beaker-project.org/5336

Comment 6 Dan Callaghan 2016-11-07 06:44:32 UTC
Beaker 23.3 has been released.


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