Getty's on serial consoles need to be consistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned | ||
util-linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
In our cloud images today we launch a getty on ttyS0, as long as it's not in a container. We don't launch a getty on ttyS1-n even if they exist.
In MAAS, which also uses cloud images, it would often be useful to put getty's on the serial port that is mapped to remote serial access, such as IPMI SOL. It is however difficult to know which is the correct getty.
Broadly speaking I think we should have a consistent approach to getty's. That might mean:
* launch a getty on each ttySn that passes an stty test (as per ttyS0 currently)
* allow cloud-init to prevent some of those, via vendordata or userdata or default behaviour per-cloud
or
* launch no getty's on ttyS, but
* allow cloud-init to create them based on vendordata or userdata or default behaviour per-cloud
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in util-linux (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Not sure if this should also be tracked against the cloud image builder.