RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
cloud-init and many other logs are directed to /dev/console. OpenStack creates VMs with a serial port, reads it and keeps a buffer of several last lines written there. the cloud-image should be configured so that the /dev/console is an "alias" of /dev/ttyS0

Version-Release number of selected component (if applicable):
rhel-server-kvm-7.0-20131217.0

How reproducible:
always

Steps to Reproduce:
1. in the booted image, try
# echo ttyS0 > /dev/ttyS0 
# echo console > /dev/console 
2. on your laptop, try
3. also, make sure the cloud-init related  messages, as the key fingerprints are output to the ttyS0, so one can safely add them to his known_hosts

Actual results:
> nova console-log --length 5 rhel-7-test               
[ 1239.470257] device-mapper: table: 252:0: linear: dm-linear: Device lookup failed
[ 1239.471055] device-mapper: ioctl: error adding target to table
ttyS0


Expected results:
...
ttyS0
console

Additional info:

Version: rhel-guest-image-7.0-20140227.0.x86_64.qcow2
Actual results:

[root@dhcp-10-124 rc3.d]# ttyS0
console

[root@dhcp-10-124 rc3.d]# echo ttyS0 >/dev/ttyS0
ttyS0
[root@dhcp-10-124 rc3.d]# echo console >/dev/console
console
[root@dhcp-10-124 rc3.d]#

And also the cloud-init related messages are output to ttyS0:
[root@dhcp-10-124 ~]# cloud-init[585]: 2014-03-02 22:00:43,462 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 113] No route to host]

We can see messages and logs are output to ttyS0.

Jaroslav,
  Do you need this bug also been fixed in rhel6? If so please clone it to rhel6.

  We can reproduce this bug on rhel-guest-image-6.5-20140307.0.x86_64.qcow2
  So I don't think it's a regression bug, do you agree?

Yes, I would like to have it sending the messages to /dev/ttyS0 on all 6.4 6.5 and 7.0

It used to be working like that on 6.4 and 6.5, sot this is a regression.

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.

http://rhn.redhat.com/errata/RHBA-2014-0754.html