Bug 1019564

Summary: Lorax should not remove the virtio_console.ko module
Product: [Fedora] Fedora Reporter: Amit Shah <amit.shah>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amit.shah, anaconda-maint-list, bcl, crobinso
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-20.3-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1019569 (view as bug list) Environment:
Last Closed: 2013-10-22 05:40:16 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:    
Bug Blocks: 1019569    

Description Amit Shah 2013-10-16 05:47:26 UTC
Description of problem:

Brian C. Lane found Lorax removes the virtio_console.ko module from the installer image; it needs to leave drivers/char/virtio_console.ko when cleaning up, to ensure kernels which build virtio_console.ko as a module are able to send guest install logs to the host via virtio-serial.

Comment 1 Fedora Update System 2013-10-17 00:22:39 UTC
lorax-20.3-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/lorax-20.3-1.fc20

Comment 2 Fedora Update System 2013-10-17 20:30:08 UTC
Package lorax-20.3-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lorax-20.3-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-19192/lorax-20.3-1.fc20
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-10-22 05:40:16 UTC
lorax-20.3-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.