When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud-init, as it tries to log to /dev/console, and is likely to break other programs.
On Focal:
root@ip-172-31-24-163:~# ls -l /dev/console
crw------- 1 root root 5, 1 Sep 21 16:07 /dev/console
root@ip-172-31-24-163:~# echo x > /dev/console
root@ip-172-31-24-163:~#
Hi,
When running Groovy daily images on i3.metal instances a broken /dev/console is created. The char device appears to be writable but writing to it causes an Input/output error. This is breaking cloud-init, as it tries to log to /dev/console, and is likely to break other programs.
On Focal:
root@ip- 172-31- 24-163: ~# ls -l /dev/console 172-31- 24-163: ~# echo x > /dev/console 172-31- 24-163: ~#
crw------- 1 root root 5, 1 Sep 21 16:07 /dev/console
root@ip-
root@ip-
On Groovy:
root@ip- 172-31- 20-184: ~# ls -l /dev/console 172-31- 20-184: ~# echo x > /dev/console
crw--w---- 1 root tty 5, 1 Sep 21 16:03 /dev/console
root@ip-
bash: echo: write error: Input/output error
The Groovy kernel log has a
[ 3.561696] fbcon: Taking over console
line in it, which is not present in the Focal kernel log (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over console?