-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
fix vlan interface bring up on boot #44347
Conversation
when the parent interface of a vlan interface is not up (yet), ip link cannot bring the vlan interface up the vlan interface will be automatically brought up when the parent interface is up later fix #28620
I am against merging this, because it is a hack, not a solution. |
Yes, it is a hack. And there're In my opinion, a solution would require moving to networkd or a sophisticated refactoring of scripted networking, which is not possible in near future. Consider #28620 has a |
This hack doesn't even explain why it's doing what it is doing in a comment in the source code. As such anyone who ever wants to implement a better method can only break everything else or hunt down GitHub (if that still is being used by the time someone gets around to implementing this). Just because the code is bad doesn't mean we need to make it worse. I am not a code owner, but that's how I -- as one of its users -- think about it. |
Is it possible to only run that command on a condition? I'd also prefer to to have a random unexplained |
A hack is better than intermittent boot failures. If the code is already using this pattern then using it once more doesn't make it worse if its omission a bug. Call it an intermediate workaround and save it for the refactoring or complete removal after swapping to networkd. |
Needs at least a comment explaining why that's needed |
What is a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As indicated.
I believe the proper networking terminology is "physical interface". I am suffering from the issue this PR seems to be solving. I have a system that more often than not fails to boot because of the interfaces being brought up in the wrong order. Since the the networking scripts are already littered with similar hacks I have trouble seeing the issue with using the same pattern once more. English isn't my first language either, but I tried to formulate a better comment below: "We try to bring up the logical VLAN interface. If the physical interface the logical interface is dependent upon is not up yet we will fail to immediately bring up the logical interface. "|| true" is a hacky workaround for this issue, resulting in the logical interface being brought up later on." |
@coretemp I agree with you but that's he mess we currently have. Refactoring those units would be a waste of time because there are already enough network configuration systems out there that do it right. We will probably move to networkd eventually. |
@GrahamcOfBorg test networking.scripted.vlan |
Success on aarch64-linux (full log) Attempted: tests.networking.scripted.vlan Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: tests.networking.scripted.vlan Partial log (click to expand)
|
@GrahamcOfBorg test networking.scripted.vlan |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Success on x86_64-linux (full log) Attempted: tests.networking.scripted.vlan Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: tests.networking.scripted.vlan Partial log (click to expand)
|
Motivation for this change
fix #28620
When the parent interface of a vlan interface is not up (yet),
ip link
cannot bring the vlan interface up. The vlan interface will be automatically brought up when the parent interface is up later.