[Bug 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)

[Scott Moser]

plymouth-disabler has been accepted into the archive.
That could be used in the cloud images to reach the desired affect, but there is some fallout.

I'd like to investigate some more actually getting the bug fixed in
plymouth and doing without plymouth-disabler.  If that should occur, we
can remove plymouth-disabler from archive.

** Also affects: plymouth-disabler (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: plymouth-disabler (Ubuntu)
   Importance: Undecided => Medium

** Changed in: plymouth-disabler (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1235231

Title:
  plymouth loses output to /dev/console (such as ci-info: messages)

Status in The Plymouth splash screen:
  Confirmed
Status in “cloud-init” package in Ubuntu:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Confirmed
Status in “plymouth-disabler” package in Ubuntu:
  Confirmed

Bug description:
  During early boot, plymouth captures writes to /dev/console.  As I
  understand it, it is supposed to re-play that content later.  Whether
  or not it intends to is not the issue.  In our cloud-images (and in
  other cases) users may write data to /dev/console that needs to be
  seen on the other side (ie a serial logger or 'get-console-ouptput'
  api call).

  See the attached 'my-logger.conf' for an upstart job that simply
  writes data early in boot to /dev/console.  Sometimes data "lost" is
  available in /var/log/boot.log, but sometimes it doesn't even seem to
  make it there.  bug 682831 has an attachment 'myhack-init' that does a
  similar thing but starts outputting by replacing /sbin/init and then
  calling /sbin/init itself.

  Related bugs:
   * bug 682831:  lost console output early in boot

  == Original bug report ==
  On precise cloud images, I get a console output line like this:

  ci-info: eth0  : 1 192.168.122.204 255.255.255.0   52:54:00:7f:d8:ca^M

  On saucy cloud images, this is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1235231/+subscriptions