Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1142241

Summary: [wgt] 3.5.3 has missing '[loggers]' section name in default-logger.ini which prevents GA running
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: Windows Guest ToolsAssignee: Lev Veyde <lveyde>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: bazulay, ecohen, gklein, iheim, rbalakri, Rhev-m-bugs, sbonazzo, sherold, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 17:43:01 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:
Bug Depends On: 1142264    
Bug Blocks:    

Description Jiri Belka 2014-09-16 12:36:24 UTC
Description of problem:

3.5.3 has missing '[loggers]' section name in default-logger.ini which prevents GA running

Log Name:      Application
Source:        RHEV-Agent
Date:          9/16/2014 1:02:59 PM
Event ID:      10
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      jb-w7-x64
Description:
The description for Event ID 10 from source RHEV-Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Traceback (most recent call last):
  File "OVirtGuestService.pyc", line 58, in __init__
  File "ConfigParser.pyc", line 286, in read
  File "ConfigParser.pyc", line 482, in _read
MissingSectionHeaderError: File contains no section headers.
file: C:\Program Files (x86)\Redhat\RHEV\Drivers\Agent\default-logger.ini, line: 2
'keys=root\n'

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="RHEV-Agent" />
    <EventID Qualifiers="49152">10</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-16T11:02:59.000000000Z" />
    <EventRecordID>1266</EventRecordID>
    <Channel>Application</Channel>
    <Computer>jb-w7-x64</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Traceback (most recent call last):
  File "OVirtGuestService.pyc", line 58, in __init__
  File "ConfigParser.pyc", line 286, in read
  File "ConfigParser.pyc", line 482, in _read
MissingSectionHeaderError: File contains no section headers.
file: C:\Program Files (x86)\Redhat\RHEV\Drivers\Agent\default-logger.ini, line: 2
'keys=root\n'</Data>
  </EventData>
</Event>

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

How reproducible:
100%

Steps to Reproduce:
1. install wgt 3.5.3
2.
3.

Actual results:
GA not running because of broken default-logger.ini

Expected results:
running

Additional info:

Comment 2 Lev Veyde 2014-09-16 13:10:23 UTC
Debugged this.

This one is caused by the broken default-logger.ini configuration file in the latest release of rhevm-guest-agent.

It's (probably) missing the d/s patch, as the base name of the log file is expected to be rhev-agent.log, not ovirt-guest-agent.log.

Note the line :
args=('ovirt-guest-agent.log', 'a+', 100*1024, 5)

It should be i.e. :
args=('rhev-agent.log', 'a+', 100*1024, 5)

Comment 6 Jiri Belka 2014-10-22 08:50:32 UTC
ok, 3.5.5

Comment 8 errata-xmlrpc 2015-02-11 17:43:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0198.html