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

Metal3 - Network interfaces - Use specific naming scheme #153

Open
rletrocquer opened this issue Sep 9, 2024 · 0 comments
Open

Metal3 - Network interfaces - Use specific naming scheme #153

rletrocquer opened this issue Sep 9, 2024 · 0 comments

Comments

@rletrocquer
Copy link

Since metal3:0:8:0 and the use of a ramdisk image based on Leap/SLES 15.6, the names of the network interfaces detected during introspection have changed
As explained by @hardys metal3 0.7.x is 15.5 based ramdisk which used systemd-249.17 while the metal3 0.8.x ramdisk is 15.6 based and used systemd-254.15

metal3:0:7:x :

network_interfaces:
      bond0:
        type: bond
        interfaces:
          - enp75s0f0
          - enp75s0f1

metal3:0.8.x :

network_interfaces:
      bond0:
        type: bond
        interfaces:
          - enp75s0f0np0
          - enp75s0f1np1

We have tried to define net.naming-scheme=v249 in IronicKernelParams without success for the moment.

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

No branches or pull requests

1 participant