Skip to content

Conversation

@ogayot
Copy link

@ogayot ogayot commented Dec 15, 2025

The installer for Ubuntu 26.04 now has the ability to create users before first boot [1]. With relevant changes to VirtualBox, it will fix the inability to install unattended when Guest Additions are also installed (see ticketref:22278).

But for that to work, we need the user parameters to be specified in the identity section, not in the user-data section (which is still processed by cloud-init on first boot).

In addition, we need to make sure the vboxsf group exists before calling usermod -aG vboxsf [...].

I don't have access to bugref:10878 so I can't tell why the user information were moved from identity to cloud-init's user-data in the first place. Please let me know if it was fixing something important?

I've tested these two patches and was able to successfully install the current daily Ubuntu 26.04 ISO with Guest Additions.
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20251214/
(the ISO we be removed in a few day, but the current daily is available at https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/).

OCA: my company membership request is under review.

ticketref:22278

[1] canonical/subiquity#2263

…r-data section in auto-install file of Subiquity. Needed to set user group correctly"

The installer for Ubuntu 26.04 now has the ability to create users before first
boot. This will fix the inability to install unattended when Guest Additions
are also installed (see ticketref:22278).

But for that to work, we need the user parameters to be specified in the
identity section, not in the user-data section (which is processed by
cloud-init on first boot).

ticketref:22278

This reverts commit 911ce9e.

Signed-off-by: Olivier Gayot <[email protected]>
…up exists before adding users to it

When installing Ubuntu, the vboxsf group does not exist when the postinstall
script executes. Ensure it does so that the usermod command can succeed.

ticketref:22278

Signed-off-by: Olivier Gayot <[email protected]>
@oracle-contributor-agreement
Copy link

Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:

To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.

When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.

If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Required At least one contributor does not have an approved Oracle Contributor Agreement. label Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Required At least one contributor does not have an approved Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant