subiquity installation ssh session is not automatically restarted after installer update

[Frank Heimes]

Today I used the daily-live image (time stamp April 20th) for a z/VM guest installation.

With that image the subiquity version 20.04.1+git44.670c9c83 is initially started and active.
I am then notified about an installer update 'Installer update available'
and when I do the update 'Update to the new installer', it's downloaded and the update performed
(I can verify this in a shell with:
snap list | grep subiquity
subiquity 20.04.2 1748 latest/stable/… canonical* classic )
But after the installer update is finished, help still shows: 20.04.1+git44.670c9c83

However, if I'm manually stopping the ssh session "~." and reconnect, help tells me I am on the updated version: 20.04.2

[Michael Hudson-Doyle (mwhudson)]

https://github.com/CanonicalLtd/subiquity/pull/741

[Frank Heimes (fheimes)]

Just retested having edge channel activated, running the installer in a ssh session (and not in a console).

The installer informed my about an update, I accepted and the update to 1865 completed.
However, the help menu told me that I'm still on:
"This is version 20.04.3 of the installer."
so I restarted the installer manually (~.)
and after the restart the installer was on:
"This is version 20.05.1 of the installer."

Hence, a restart seems to be still needed.

[Michael Hudson-Doyle (mwhudson)]

Ah yes, the fix only applies for upgrades *from* the fixed version. So it won't really help until we spin new media, i.e. 20.04.1.