Skip to content

Always write the user-data file on the NoCloud datasource - #21

Open
fw2568 wants to merge 1 commit into
mainfrom
fix/always-write-user-data
Open

fw2568 wants to merge 1 commit into
mainfrom
fix/always-write-user-data

Conversation

@fw2568

@fw2568 fw2568 commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Recent cloud-init versions treat user-data as a required part of the NoCloud datasource (pp2d_kwargs = {"required": ["user-data", "meta-data"], ...}). NoCloudDataSource.GenerateConfigDriveContent skipped the user-data file entirely when no user-data was supplied, so cloud-init aborted reading the datasource and did not even apply the network configuration.

The file is now always written. An empty user-data serializes to an empty multipart message, which cloud-init accepts.

Recent cloud-init versions treat user-data as a required part of the
NoCloud datasource (pp2d_kwargs required: user-data, meta-data). When no
user-data was supplied, the data source skipped the file entirely, so
cloud-init aborted and did not even apply the network configuration.

Always write the user-data file; an empty user-data serializes to an
empty multipart message, which cloud-init accepts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant