Bug 1048776 - /virt/install: Duplicated data in console logs on RHEL5 xen guests
Summary: /virt/install: Duplicated data in console logs on RHEL5 xen guests
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: tests
Version: 0.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.15.3
Assignee: Nick Coghlan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-06 10:35 UTC by Jan Stancek
Modified: 2018-02-06 00:41 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-03 05:03:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Stancek 2014-01-06 10:35:56 UTC
Description of problem:
Console logs on RHEL5 xen guest are duplicated after each reboot.

Problem is that when xen guest restarts, "virsh console" process on host will end. zrhel5_write_consolelogs.py will restart it, but output is getting appened to console log file. "logguestconsoles.c" will notice this via inotify IN_CLOSE_WRITE and resets file offset to begining, which is wrong, because file wasn't truncated. As result same data will be uploaded again.

Proposed patch: http://gerrit.beaker-project.org/#/c/2630/

Version-Release number of selected component (if applicable):
distribution-distribution-virt-install-4.0-79

How reproducible:
100%

Steps to Reproduce:
1. install RHEL5 xen guest
2. make couple reboots

Actual results:
data in console log is duplicated
for example, following message is present in logs multiple times:
12/13/13 18:55:14  JobID:561449 Test:/distribution/install Response:1

Expected results:
data in console log is not duplicated after reboot

Additional info:
https://lists.fedorahosted.org/pipermail/beaker-devel/2013-December/000917.html

Comment 7 Nick Coghlan 2014-02-03 05:03:09 UTC
This change has now been published as http://beaker-project.org/tasks/distribution-distribution-virt-install-4.0-80.noarch.rpm


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