Bug 821948 - [BUG] fails to clear console logs
Summary: [BUG] fails to clear console logs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-15 20:40 UTC by Bill Peck
Modified: 2019-05-22 13:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-26 06:40:35 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 835373 0 urgent CLOSED console logs are not cleared when manually provisioning 2021-02-22 00:41:40 UTC

Internal Links: 835373

Description Bill Peck 2012-05-15 20:40:19 UTC
Description of problem:
regression from 0.8 where we cleared console logs before install.

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

Comment 1 Dan Callaghan 2012-05-16 06:29:47 UTC
On Gerrit: http://gerrit.beaker-project.org/1073

Comment 3 Dan Callaghan 2012-06-19 06:11:15 UTC
The clear_logs command we added for this does work, but not always in time. The command might not have run before beaker-watchdog starts monitoring the console log, in which case the old log (before truncation) will be uploaded to Beaker and the new log will never be visible (because after truncation it is shorter than the log already uploaded).

We probably need to make this synchronous. Or else make the watchdog code do the truncation before it starts monitoring the log.

Comment 5 Dan Callaghan 2012-06-21 12:16:14 UTC
Second try posted to Gerrit: http://gerrit.beaker-project.org/1160

Comment 6 Dan Callaghan 2012-06-21 22:29:00 UTC
This bug has been addressed in Beaker 0.9.0-3 which is currently running on stage:

https://beaker-stage.engineering.redhat.com/

Comment 7 Dan Callaghan 2012-06-26 06:40:35 UTC
Beaker 0.9.0 has been released.


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