The code causing the failure (which Paride linked to) does specifically
know that the output is destined for /dev/console:
if console:
conpath = "/dev/console"
if os.path.exists(conpath):
with open(conpath, 'w') as wfh:
wfh.write(text)
wfh.flush()
I agree that we should not generically ignore issues with writing, but
this would be a targetted fix for specifically this case.
The general issue here, AIUI, is that the kernel command line and the
cloud have to be in agreement about how /dev/console is configured: if
the kernel command line specifies a console then the kernel will
configure one, even if there is no corresponding console provided by the
cloud. On first boot, users have no way of aligning the kernel's
default configured console with the console that the cloud provides (or,
rather, the lack thereof), so cannot do anything to avoid this
traceback.
(Cloud-specific Ubuntu images generally have this configured correctly,
but if you're bringing a generic cloud image to $platform, then there's
no guarantee that they will be aligned.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error: /dev/console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
