Better handling for the multi-console scenario
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| subiquity |
New
|
Undecided
|
Unassigned | ||
Bug Description
Somehow related to LP: #1852730.
By design subiquity starts on all the consoles available on the machine. This could be confusing for the user, as connecting to a different console (think of connecting to a tty and a serial console of a VM) leads to two different subiquities potentially in a different state. When this first happened to me I thought there was something wrong and the installation process was reset, as it is not immediate to realize that there is 1 subiquity running *per console*, and not 1 subiquity showing up on the different console.
I think that when the install process begins the other subiquities should be killed; for example the first subiquity with a meaningful user interaction could send a SIGUSR1 to all the other subiquities, which can then exit printing a meaningful message.
| Paride Legovini (paride) wrote | #1 |
| Michael Hudson-Doyle (mwhudson) wrote | #2 |
| Paride Legovini (paride) wrote | #3 |
When I wrote the original report I was under the wrong impression that the AutoInstall feature was going to be an extension of the existing "preseeded" installs with an answers.yaml.
As this is is not the case, and as the answers.yaml "preseed" is (in my understanding) not meant to be a user-facing feature, it is probably less important to have its rough edges smoothed, and we probably want to favor simplicity in its implementation.
I'm fine with closing this report entirely if you think this isn't going to be implemented.