Red Hat Bugzilla – Bug 820106
anaconda transfers all guest anaconda logs into syslog on host with virtio and rsyslog
Last modified: 2013-01-10 01:46:44 EST
Created attachment 583174 [details]
syslog transferred to host
Description of problem:
This follows the introduction http://fedoraproject.org/wiki/Anaconda/Loggingto transfer all guest anaconda logs to the guest by virtio and rsyslog. But all the anaconda logs are crashed into syslog and there is only syslog file exists in the host directory.
Version-Release number of selected component (if applicable):
F17 Final TC3
Steps to Reproduce:
1.create a guest
2.edit guest define xml file, add the following into it.
<source mode='connect' host='127.0.0.1' service='6080'/>
<target type='virtio' name='org.fedoraproject.anaconda.log.0'/>
3. start the rsyslog with analog.py script in attachment by running
$ eval `scripts/analog -p 6080 -s -o ./rsyslogd.conf /tmp/autoqa/log`
4. restart guest and proceed the installation.
5. there is only file 'syslog' in directory /tmp/autoqa/log/anaconda
only syslog file exists and all logs are crashed into it.
all guest anaconda logs are transferred to the host.
Created attachment 583190 [details]
anaconda log on guest
Created attachment 583191 [details]
program log on guest
Created attachment 583192 [details]
syslog on guest
Created attachment 583193 [details]
So basically different events are no longer split into different log files, instead all of them are merged into one.
I have compared attached analog.py and the upstream one , and they are not fully equal, but there seems to be only slight changes that should not have any big impact.
Now the question is - is anaconda logging important for some use cases, so that we definitely need to have this fixed in F17 Final? For example does Beaker or some other tools rely on it?