Red Hat Bugzilla – Bug 745711
virtio cannot transfer all guest anaconda logs to host
Last modified: 2014-09-30 19:40:33 EDT
Cloning this to propose as an F16 blocker.
+++ This bug was initially created as a clone of Bug #744544 +++
Created attachment 527084 [details]
Description of problem:
It fails to transfer all anaconda logs of guest to the host by serial virtio. only the syslog is transferred.
Version-Release number of selected component (if applicable):
host is F15 with libvirt-0.8.8-7.fc15.x86_64, virt-manager-0.8.7-6.fc15.noarch
guest is F16 Beta gold (F16 beta rc4)
Steps to Reproduce:
1. add virtio-serial port on the guest with virsh edit
2. run analog to start listening to the guest
3. start guest
This blocks the Fedora installation test automation project, hope you can give it high priority. Thanks.
--- Additional comment from email@example.com on 2011-10-09 06:42:54 EDT ---
Created attachment 527085 [details]
--- Additional comment from firstname.lastname@example.org on 2011-10-10 11:14:02 EDT ---
I can confirm this, though this is not a bug in analog. Apparently the rsyslog format of forwarded messages has changed between the two versions and what is forwarded from F16 rsyslogd (the one running in your guest) is not correctly parsed by the receiving F15 rsyslogd (the one where analog is running). You should be able to confirm this e.g. by looking at debug_unknown_source.log which contains all the messages where we failed to recognize the tag.
Reassigning to rsyslogd which maintainer might or might not be able to help you.
The easiest fix for you is in any case upgrading your host rsyslogd to the same version the tested guest is running.
--- Additional comment from email@example.com on 2011-10-11 09:09:02 EDT ---
We clarified this with theinric and the error is not because of a new rsyslog version but rather due to changed environment in F16 --- something we can fix in the image generation.
--- Additional comment from firstname.lastname@example.org on 2011-10-11 09:57:21 EDT ---
Patch posted: https://www.redhat.com/archives/anaconda-devel-list/2011-October/msg00065.html
--- Additional comment from email@example.com on 2011-10-12 04:28:23 EDT ---
Fixed by e61f3b23d47903b30ac0ce591a200dc5edc4f979. This will be part of the first f17 compose.
Will it be OK to have this in F17 only?
--- Additional comment from firstname.lastname@example.org on 2011-10-12 22:24:09 EDT ---
(In reply to comment #5)
> Fixed by e61f3b23d47903b30ac0ce591a200dc5edc4f979. This will be part of the
> first f17 compose.
> Will it be OK to have this in F17 only?
It would be better if you can correct it in F16 Final, since the new environment in F16, I have to update the test scripts accordingly, so I need a working media to test. Thanks.
I pushed this to f16-branch in lorax as b0e5b51be7cc5ca362612c0fe212814a2886a4cf. The only way to ensure this is going to make f16 is to have this accepted as a NTH. Proposed as such: the fix allows the autoQA project Hongqing is working on to continue.
Discussed at 2011-10-14 NTH review meeting. As mentioned in some bugs last week, we cannot base our NTH decisions on anaconda commit policies: this bug is not significant enough to warrant touching anaconda in a freeze, and hence we reject it as NTH. For AutoQA we can build custom images if necessary.