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

[11.0 stable] Do not try to use invalid network config #3977

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

milan-zededa
Copy link
Contributor

Backport of #3940 to 11.0

Even if zedagent detects invalid network config and reports DPC with
error, NIM may still try to use it, run connection tests and overwrite
the error with another or even with nil.
Instead, NIM should skip mgmt ports with invalid config and preserve the
error (incl. across reboots).
Similarly, DPC reconciler should not try to apply invalid config into
the network stack.
Additionally, diag was extended to report when port config is not valid.
Lastly, readability of some parsing error messages was improved.

Signed-off-by: Milan Lenco <milan@zededa.com>
(cherry picked from commit 2beb07e)
@milan-zededa
Copy link
Contributor Author

Note that I'm not going to backport this to 10.4. There are so many differences between 10 and 11 that I cannot just cherry-pick this commit but effectively would have to create it from the scratch. Given that this is not a very important fix/improvement, I believe that such effort is not worth it.

Copy link
Contributor

@eriknordmark eriknordmark left a comment

Choose a reason for hiding this comment

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

LGTM (and yetus complaints are about code not modified in this PR so we'll ignore them)

@milan-zededa
Copy link
Contributor Author

Please note that separately (not related to this PR) I'm looking why the metadata test started failing so often now..

@eriknordmark eriknordmark merged commit 7cc28f2 into lf-edge:11.0-stable Jun 12, 2024
20 of 29 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
Development

Successfully merging this pull request may close these issues.

2 participants