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

network: recreate link if its interface name is changed #8795

Merged
merged 1 commit into from
Apr 26, 2018

Conversation

yuwata
Copy link
Member

@yuwata yuwata commented Apr 24, 2018

If an interface name is changed, then the link state, especially managed or not, may need to be updated, as its corresponding .link or .network files may be different. So, let's once drop the link and recreate a new link object.

Fixes #8794. Also this may fix #7920.

If an interface name is changed, then the link state, especially
managed or not, may need to be updated, as its corresponding
.link or .network files may be different. So, let's once drop
the link and recreate a new link object.

Fixes systemd#8794.
@yuwata
Copy link
Member Author

yuwata commented Apr 24, 2018

Re-creating a link may be overkill, but I am not sure about what kind of information needs to be updated when an interface name is changed.
Note that I've tested with ip link command as written in #8794. At least with ip link command, to rename an interface, it is necessary to make the interface down. So, this may be overkill, but I hope this merely causes unwanted effects.

@poettering
Copy link
Member

KVM: entry failed, hardware error 0x0
EAX=00000000 EBX=00000000 ECX=00000000 EDX=000206c1
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0

CI failure appears unrelated, merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants