Comment 19 for bug 1473527

There are a slew of bugs and apparently random fallout of /dev/console not working.
In my opinion, its really *not* helpful to just ignore that 'write' to stdout fails. Ignoring errors is never really a solution. In this case, cloud-init may have specifically opened /dev/console. But in other cases, it just writes to its stdout or stderr. It does not know that that output is destined for /dev/console or a file, and should not just ignore the errors.

The real fix for this is to fix the kernel or the OS in some way so that writes to /dev/console always succeed.