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

[13.4-stable] Set WType even for wireless ports without network config #4369

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

milan-zededa
Copy link
Contributor

nim, zedrouter and other microservices depend on the WType port attribute to recognize wireless network port. This is needed even in cases where the wireless adapter is not really used and has no network config attached. Otherwise, we may get to situation where we try to bridge a wireless adapter or perform some other invalid operation, especially after the switch NI enhancements done in: 7a6981b

In the case wireless config is not present, we can get the physical port type from the device model and set WType accordingly.

Signed-off-by: Milan Lenco [email protected]
(cherry picked from commit 610b4ac)

nim, zedrouter and other microservices depend on the WType port
attribute to recognize wireless network port. This is needed even in
cases where the wireless adapter is not really used and has no network
config attached. Otherwise, we may get to situation where we try to
bridge a wireless adapter or perform some other invalid operation,
especially after the switch NI enhancements done in:
7a6981b

In the case wireless config is not present, we can get the physical port
type from the device model and set WType accordingly.

Signed-off-by: Milan Lenco <[email protected]>
(cherry picked from commit 610b4ac)
@OhmSpectator
Copy link
Member

Our GH Actions do not like when the source branch has the same name as the target branch, I guess =(

Copy link
Member

@OhmSpectator OhmSpectator left a comment

Choose a reason for hiding this comment

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

I believe it's a 1-to-1 cherry-pick of a commit that has already been reviewed...

@milan-zededa
Copy link
Contributor Author

I believe it's a 1-to-1 cherry-pick of a commit that has already been reviewed...

Correct

@rene
Copy link
Contributor

rene commented Oct 17, 2024

I believe it's a 1-to-1 cherry-pick of a commit that has already been reviewed...

That's correct @OhmSpectator , I've seen these kind of errors before....

@OhmSpectator
Copy link
Member

Our GH Actions do not like when the source branch has the same name as the target branch, I guess =(

@yash-zededa do you think we can quickly fix it?

@OhmSpectator OhmSpectator merged commit 8cddcb1 into lf-edge:13.4-stable Oct 17, 2024
34 of 38 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.

3 participants