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

[Scott Moser]

Using a build from current lp:ubuntu/plymouth that has steve's fix for
bug 1160079 inside it, I no longer am losing data written to the
console!

I've tested this in a trusty kvm local image.
disk-patched.img had the new debs installed
disk-unpatched.img did not.
both images had https://bugs.freedesktop.org/attachment.cgi?id=89759 run on them (so the logging init-wrapper was in place).

$ cat go-test.txt
LOG="out.log"
rm -f "$LOG"
i=0
while i=$(($i+1)) && [ $i -le 10 ]; do
  echo "---- $(date) $i ----" >> "$LOG"
  for r in patched unpatched; do
    qemu-img create -f qcow2 -b disk1-$r.img disk1.img
    slog=$(printf "serial-%s-%02d.log" "$r" "$i")
    echo "---- $(date) $i $r ----" >> "$LOG"
    kvm -net nic -net user,hostfwd=tcp::2222-:22 \
       -drive file=disk1.img,if=virtio -drive file=seed.img,if=virtio \
       -serial "file:$slog" -vga none -nographic
  done
done

echo "--- $(date) FINISHED ---" >> "$LOG"

$ cat user-data 
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
power_state:
 mode: poweroff
 message: "Bye Bye"

$ for f in serial-*.log; do echo $f: $(grep "XX:" $f | wc -l); done
serial-patched-01.log: 103
serial-patched-02.log: 103
serial-patched-03.log: 103
serial-patched-04.log: 103
serial-patched-05.log: 103
serial-patched-06.log: 103
serial-patched-07.log: 103
serial-patched-08.log: 103
serial-patched-09.log: 103
serial-patched-10.log: 103
serial-unpatched-01.log: 80
serial-unpatched-02.log: 82
serial-unpatched-03.log: 81
serial-unpatched-04.log: 80
serial-unpatched-05.log: 79
serial-unpatched-06.log: 84
serial-unpatched-07.log: 80
serial-unpatched-08.log: 83
serial-unpatched-09.log: 82
serial-unpatched-10.log: 82

-- 
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