-
Notifications
You must be signed in to change notification settings - Fork 127
Change interface name after enabling predicted interface names #1561
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
base: main
Are you sure you want to change the base?
Change interface name after enabling predicted interface names #1561
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
feec983
to
116ac5a
Compare
116ac5a
to
335a12a
Compare
/test metal3-centos-e2e-integration-test-main |
45b67e9
to
f5b3b1f
Compare
19a6fd7
to
71733a2
Compare
71733a2
to
3934126
Compare
/hold |
Can you document in the PR description what is the value of this change? |
Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
3934126
to
e34124a
Compare
This PR makes changes to interface names after enabling predictable interface names in node images.
We have build centos node images with kernel parameter "net.ifnames=0", as a result we had interface names eth0, eth1 on centos nodes.
On project infra PR we are changing this parameters "net.ifnames=1". Now interface names will be predicted. Stable names based on hardware information. enp1s0, eno1.