Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Late commands vs done #2013

Merged
merged 3 commits into from
Jun 25, 2024
Merged

Late commands vs done #2013

merged 3 commits into from
Jun 25, 2024

Conversation

dbungert
Copy link
Collaborator

No description provided.

Copy link
Member

@ogayot ogayot left a comment

Choose a reason for hiding this comment

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

I would like to separate the removal of the unattended-upgrades cancellation from the late-commands status change. I will split the commits into two accordingly.

subiquity/common/types/__init__.py Outdated Show resolved Hide resolved
Today, late-commands can in some cases not actually run, if the
application reports a DONE state and a reboot is permitted.

We now add LATE_COMMANDS to track this explicit state - we no longer
transition to a DONE state while these commands are running.
Last cycle, to make the installation faster, we decided to disable the
unattended-upgrades minimal steps. This prevents proper handling of
unattended-upgrades cancellation so we now drop the feature completely.

Furthermore, the status reported on the text installer UI is misleading
when unattended-upgrades is running.
@ogayot
Copy link
Member

ogayot commented Jun 20, 2024

So I just tested this PR against the desktop installer. Although the meta/status reports {"state": "LATE_COMMANDS"}, the UI would still show the Installation complete screen (and the restart now button). So it requires more work.

NOTE: This was related to how I injected the new subiquity code into an existing ubuntu-desktop-bootstrap snap without regenerating the types. Dennis confirmed that the fix was working after regenerating the types.

…ommand

Since we removed the ability to interrupt the unattended-upgrades
process, we can use run_curtin_command instead of start_curtin_command.

Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
@ogayot ogayot marked this pull request as ready for review June 24, 2024 09:49
Copy link
Collaborator Author

@dbungert dbungert left a comment

Choose a reason for hiding this comment

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

LGTM. I can't Approve since I opened the PR ;)

@ogayot ogayot merged commit de63f57 into canonical:main Jun 25, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants