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

networkd units not supported in ign-converter #741

Closed
pothos opened this issue May 13, 2022 · 2 comments · Fixed by flatcar-archive/coreos-overlay#1910
Closed

networkd units not supported in ign-converter #741

pothos opened this issue May 13, 2022 · 2 comments · Fixed by flatcar-archive/coreos-overlay#1910
Labels
kind/bug Something isn't working

Comments

@pothos
Copy link
Member

pothos commented May 13, 2022

Description

There was a bug report on Matrix that networkd units in a v2 config didn't get translated to v3 by ign-converter (i.e., when our Ignition sees a v2 config and lifts it to v3 internally).

Impact

Either broken networking or the instance fails to boot? Didn't check

Environment and steps to reproduce

Expected behavior

The v2 networkd unit (either a unit file or a drop-in) should be converted to a plain file entry in v3.

Additional information

@tormath1
Copy link
Contributor

as a follow-up action, we should update our doc to reflect this breaking change (like: https://www.flatcar.org/docs/latest/provisioning/ignition/network-configuration/)

@tormath1
Copy link
Contributor

PR has been merged - and the fix should be available in the next beta / alpha release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants