Skip to content

Conversation

adberger
Copy link

@adberger adberger commented Aug 22, 2025

What this PR does / why we need it:

Changes originally from #475

  • CoreOS Cloud Init is not reading the drop-ins sections in cloud-config.yml since Flatcar 3975.2.0, so we switch to drop_ins.
  • CoreOS Cloud Init is not correctly templating the drop-ins sections because of a wrong condition ({{ if $unit.Content }} instead of {{ if $unit.DropIns }} or {{ with $unit.DropIns }})

Which issue(s) this PR fixes:

Fixes #1567

What type of PR is this?

/kind bug

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). kind/bug Categorizes issue or PR as related to a bug. labels Aug 22, 2025
@kubermatic-bot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Aug 22, 2025
@kubermatic-bot
Copy link
Contributor

Hi @adberger. Thanks for your PR.

I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubermatic-bot kubermatic-bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 22, 2025
@kron4eg
Copy link
Member

kron4eg commented Aug 22, 2025

/ok-to-test

@kubermatic-bot kubermatic-bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 22, 2025
@kron4eg
Copy link
Member

kron4eg commented Aug 22, 2025

osm-fail.txt
here's the fail log

@kubermatic-bot kubermatic-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 23, 2025
@adberger adberger changed the title chore: add drop_ins in addition to drop-ins, fix: templating of DropIns chore: switch from drop-ins to drop_ins, fix: templating of DropIns Aug 23, 2025
@adberger
Copy link
Author

@kron4eg

I found and fixed the error.
I also found a second conditional error.

I refrained from adding both drop-ins & drop_ins, since @jepio said:

Yes, the canonical name of that section was always drop_ins but the old yaml parser performed automatic conversion for drop-ins. This isn't supported in newer parser versions. It's also unfortunate that the examples in docs used drop-ins.

So it should be backwards compatible.

Copy link
Member

@kron4eg kron4eg left a comment

Choose a reason for hiding this comment

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

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 23, 2025
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 1a3b441930423518044da598bbc63d1f4c0118f2

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. docs/none Denotes a PR that doesn't need documentation (changes). kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cloud Init not reading drop-ins sections since Flatcar 3975.2.0.
3 participants