Installer Ubuntu-220.4.1-server after Server Snap menue jumps back to Language selection instead of Finish&Reboot

The is the Language menu to that the Installer jumps after clicking on "Done" in the Server Snap menu.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1986674/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Can you dig some log files from /var/log/installer or crash files from /var/crash if there are any?

Folder /var/crash/ is empty.

Attached the complete folder /var/log/installer/ as Tarball.

The action begins at log timestamp today 07:57, this is when completing the "SSH" and "Snap" menu, afterwards the Installer jumps back to language menu.

The log entries from timestamp yesterday are from the begin of the installation. I made a VM snaphost (including RAM) at the "SSH" menu step (so just before the bug occurs), and started from that snapshot today.

Can anybody confirm? Anything in the logfiles to see?

I think this is some kind of UI race that's causing SnapListController.done to be called twice. Does it happen every time?

It happened all first three times when I started using the ubuntu-22.04 cd .1 release. Then I made a VM snapshot at the ssh menu, just before the bug happens. But when starting from the VM snapshot, the bug only happens roughly every third try. I have the suspicion it could depend on how fast you hit enter("done") in the menu.

I think this bug is caused by this patch: https://github.com/canonical/subiquity/commit/ee528fe6a739eedc598be2af9f7e7cc8a731acdf, and more specifically this change:

         if data.status == SnapCheckState.FAILED:
- # If loading snaps failed or the network is disabled, skip the
- # screen.
- raise Skip()
+ # If loading snaps failed or network is disabled, skip the screen.
+ log.debug('snaplist GET failed, mark done')
+ self.done([])
         return SnapListView(self, data)

The removal of the raise statement makes the function always return a view, even though we move to the next screen through self.done([])

This triggers a race condition that will sometimes show the view returned, with invalid data.

https://github.com/canonical/subiquity/pull/1413

Will a new install ISO file be released?

Hello @daku8938,

Most likely not, but once a new version of Subiquity that includes this fix is released, the installer will offer to self update, through a menu like the below:

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  Installer update available [ Help ]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
  Version XXXXXXX of the installer is now available (22.07.2 is currently
  running).

  You can read the release notes for each version at:

                 https://github.com/canonical/subiquity/releases

  If you choose to update, the update will be downloaded and the installation
  will continue from here.

                        [ Update to the new installer ]
                        [ Continue without updating ]
                        [ Back ]

Choosing [ Update to the new installer ] will pickup the fix.

Olivier, our servers do not have direct internet access. They need to use a http proxy.
Can one set the http proxy first and then update the installer itself, before doing the rest of the installation configuration?

Generally, I think the installer should work properly without internet connection.

The bugfixes we're doing now, including this one, will be included in the next normally scheduled ISO builds. So for 22.04, this fix should be included in 22.04.2 ISOs.

It's our policy to stick to the LTS releases for stability reasons.
So then we cannot use the 22.04.2 ISOs, correct?
Could be released a e.g. 22.04.1.1 LTS release with this bug fixed?

I mean, what is the reason for a long term support installer CD that has this show stopping bug?

The 22.04.2 ISO would be a LTS, it's just not soon - due Feb 2023 per https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906

I have seen in the past that fully offline installs may work better - is that the case here? By that I mean, do you get better results if you skip proxy configuration and sort that out later? In no way do I like that as a long term plan, just trying to get you unstuck.

We believe a fix for this can be found in Subiquity 22.10.1. On
install you will be offered to update to the new version of the
installer if network is available, or you can perform a manual update
by running the follwing in a terminal:
sudo snap refresh subiquity