[ifupdown] Fix bridges down at boot with Debian bookworm systemd #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With Debian bookworm systemd 252.6-1, the bridge is stopped immediately after attempting its startup. It could be that this newer systemd removed the unexpected behavior that allowed to start the service while its "BindsTo" device does not exists. (cherry picked from commit 140db62)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With Debian bookworm systemd 252.6-1, the bridge is stopped immediately after attempting its startup.
It could be that this newer systemd removed the unexpected behavior that allowed to start the service while its "BindsTo" device does not exists.
(cherry picked from commit 140db62)