Bug 821948
Summary: | [BUG] fails to clear console logs | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Bill Peck <bpeck> |
Component: | lab controller | Assignee: | Dan Callaghan <dcallagh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.9 | CC: | bpeck, dcallagh, rmancy, stl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-26 06:40:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill Peck
2012-05-15 20:40:19 UTC
On Gerrit: http://gerrit.beaker-project.org/1073 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. Second try posted to Gerrit: http://gerrit.beaker-project.org/1160 This bug has been addressed in Beaker 0.9.0-3 which is currently running on stage: https://beaker-stage.engineering.redhat.com/ Beaker 0.9.0 has been released. |