Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

Initial autoinstall support #1412

Merged
merged 4 commits into from
Feb 21, 2023
Merged

Initial autoinstall support #1412

merged 4 commits into from
Feb 21, 2023

Conversation

jpnurmi
Copy link
Contributor

@jpnurmi jpnurmi commented Feb 16, 2023

  • The existing (welcome-like) loading screen is reused until we have a design for a proper loading screen that needs to be shown on startup until we get a status response from subiquity.
  • If Subiquity requires a confirmation (no "autoinstall" kernel cmdline), the wizard jumps straight to the Write changes to disk page and after that, to the installation slides.
  • If Subiquity does not required a confirmation ("autoinstall" was supplied on the kernel cmdline), the wizard jumps straight to the installation slides.
Startup Confirm Auto
image image Screenshot from 2023-02-17 18-17-55

NOTE: Semi-automated installation with interactive sections is not supported, yet.

@jpnurmi jpnurmi force-pushed the autoinstall branch 3 times, most recently from 3e8890b to 64dd345 Compare February 17, 2023 17:12
@jpnurmi jpnurmi marked this pull request as ready for review February 17, 2023 17:12
@jpnurmi

This comment was marked as outdated.

jpnurmi added a commit to jpnurmi/ubuntu-desktop-installer that referenced this pull request Feb 20, 2023
Split off from canonical#1412 and coupled with a unit test.

Make sure to call `GET /storage/v2?wait=true` before calling
`GET /storage/v2/orig_config` because only the former blocks until
Subiquity is done probing the hardware.

The correct order is important in autoinstall mode because the GUI jumps
straight to the confirmation screen after establishing a connection.
Subiquity might be still probing the hardware in the background at that
point.
jpnurmi added a commit that referenced this pull request Feb 20, 2023
Split off from #1412 and coupled with a unit test.

Make sure to call `GET /storage/v2?wait=true` before calling
`GET /storage/v2/orig_config` because only the former blocks until
Subiquity is done probing the hardware.

The correct order is important in autoinstall mode because the GUI jumps
straight to the confirmation screen after establishing a connection.
Subiquity might be still probing the hardware in the background at that
point.
Copy link
Member

@d-loose d-loose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@jpnurmi jpnurmi merged commit e75c9d3 into canonical:main Feb 21, 2023
@jpnurmi jpnurmi deleted the autoinstall branch February 21, 2023 15:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants