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

[Scott Moser]

irc conversation response to comment 21.

11/21/13 14:24:54 <smoser> so would you NAK a proposal to put 'plymouth-disabler' into 'plymouth' packaging ?
11/21/13 14:25:15 <smoser> i'd like to get that in quick and be done with it. and it really has nothing to do with cloud-init, but everythign to do with plymouth.
11/21/13 14:28:26 <slangasek> I think it's wrong to put it there, because it's about plymouth not being a proper fit for the cloud images, so why shouldn't it be in a package maintained by the cloud team
11/21/13 14:28:58 <slangasek> I see your point that it doesn't really fit cloud-init - maybe a separate source package that's seeded directly in the cloud images?
11/21/13 14:29:09 <smoser> its about fixing a bug in plymouth
11/21/13 14:29:15 <smoser> a dataloss bug
11/21/13 14:29:35 <smoser> i'm fine to make a separate sourc epakcage
11/21/13 14:29:38 <smoser> and seed it into cloud images
11/21/13 14:30:00 <smoser> but i think that means maintenance that isn't obvious should a plymouth upstart job be added.
11/21/13 14:30:05 <smoser> thats why i wanted it in plymouth.
11/21/13 14:30:27 <slangasek> right, but there shouldn't be any more plymouth jobs added
11/21/13 14:30:36 <slangasek> so the risk there is minmial
11/21/13 14:30:38 <slangasek> minimal too
11/21/13 14:31:46 <smoser> alright then. new source package :-(.

-- 
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 “cloud-init” package in Ubuntu:
  Confirmed
Status in “plymouth” 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/ubuntu/+source/cloud-init/+bug/1235231/+subscriptions