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

Prevent bonding issue by removing extra network interface from bridge_ports on sle12 autoyast #19726

Merged
merged 1 commit into from
Jul 18, 2024

Conversation

Julie-CAO
Copy link
Contributor

@Julie-CAO Julie-CAO commented Jul 12, 2024

The incorrect network bridge configuration is causing problem:

The machine bare-metal2.oqa.prg2.suse.org act as router and created illegal duplicate traffics for gateway of the oqa.prg2.suse.org subnet.
We sow "DUP" responses for ping toward vlan gateway 10.145.10.254 not just in k2 VM but also in other machines like for example on DHCP servers.

We investigated the traffics and found evidences about problematic traffics in J11 TOR switches specifically on port 5 on both TORs. ports are used by the server bare-metal2.oqa.prg2.suse.org as eth0 and eth1 see: https://racktables.nue.suse.com/index.php?page=object&object_id=23403
Our suspicion is incorrect setup bond between eth0 and eth1 interfaces that want to be LACP bond, but that is not setup on our side and in he end act as loop in this vlan.
bare-metal2:/etc/sysconfig/network # cat ifcfg-br0
BOOTPROTO='dhcp'
BRIDGE='yes'
BRIDGE_FORWARDDELAY='15'
BRIDGE_PORTS='eth0 eth1 em1 em2'
BRIDGE_STP='off'
STARTMODE='auto'

The culprit is BRIDGE_PORTS='eth0 eth1 em1 em2'. "make a bridge from two interfaces is bad practice"

@Julie-CAO Julie-CAO changed the title [WIP]Prevent bonding issue by removing extra network interface from bridge_ports on sle12 autoyast Prevent bonding issue by removing extra network interface from bridge_ports on sle12 autoyast Jul 12, 2024
@Julie-CAO Julie-CAO force-pushed the julie/eth0 branch 2 times, most recently from aea43b8 to 24faeaf Compare July 16, 2024 09:01
@Julie-CAO
Copy link
Contributor Author

Julie-CAO commented Jul 16, 2024

The verification runs with the new introduced setting BRIDGE_PORT:
sle12sp5_kvm_on_unreal3
sle12sp5_kvm_on_gonzo
sle12sp5_kvm_on_amd-zen3
sle12sp5_kvm_on_blackbauhinia
sle12sp5_kvm_on_ph052

And please merge this PR after https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/867 is merged.

@Julie-CAO
Copy link
Contributor Author

Julie-CAO commented Jul 16, 2024

FYI. The MU sle12 autoyast template has the similar problem. It will not bring troubles if there will always be one cable connection to the master Ethernet card on machines, but I'd like to raise this problem here to bring your awareness. @alice-suse @waynechen55 @RoyCai7 @tbaev @martinsmarcelo

  <networking>
    <keep_install_network config:type="boolean">true</keep_install_network>
    <managed config:type="boolean">false</managed>
    <interfaces config:type="list">
      <interface>
        <device>br0</device>
        <bootproto>dhcp</bootproto>
        <bridge>yes</bridge>
        <bridge_forwarddelay>0</bridge_forwarddelay>
        <bridge_ports>eth0 eth1</bridge_ports>
        <bridge_stp>off</bridge_stp>
        <startmode>auto</startmode>
      </interface>
    </interfaces>
  </networking>

Copy link
Contributor

@alice-suse alice-suse left a comment

Choose a reason for hiding this comment

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

lgtm, thanks for the quick fix

@alice-suse alice-suse merged commit 589f8fb into os-autoinst:master Jul 18, 2024
10 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.

4 participants