Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-43352

Assisted installer cluster installation fails with IP collision validation, due to a Porxy ARP request.

    • Moderate
    • None
    • AI-51, AI-52, AI-53
    • 3
    • False
    • Hide

      None

      Show
      None
    • Customer Escalated

      Description of problem:

           In Agent-Base Installation, storage network on all nodes will be also configured. If both VLAN interfaces in the same L3 switch used as gateways for compute cluster management and storage networks of the OCP cluster have arp-proxy enabled, then the IP collisions validation will report errors. The reason why the IP collision validation fails is that the validation seems to send the arp-request from both interfaces bond0.4082 and bond1.2716 for all addresses used for compute cluster management and storage networks.

      Version-Release number of selected component (if applicable):

      4.14    

      How reproducible:

          Always

      Steps to Reproduce:

          1. Install cluster using Agent-base with proxy enabled.
          2.  Configur both VLAN interfaces in the same L3 switch, used as gateways for compute cluster management and storage networks of the OCP cluster have arp-proxy enabled 
          

      Actual results:

          IP collision validation fails, the validation seems to send the arp-request from both interfaces bond0.4082 and bond1.2716 for all addresses used for compute cluster management and storage networks.  The validation seems to trigger the arp-requests sent out from all NICs of the nodes. If the gateways connected to the different NICs of the node have arp-proxy configured, then the IP collision failure will be observed.

      Expected results:

          Validation should pass in Arp Porxy Scenario 

      Additional info:

          In arp-proxy scenario, the arp reply is not needed from the NIC which IP address is not in the same subnet as the destination IP address of the arp-request. Generally speaking, when the node tries to communicate to any destination IP address in the same subnet as the IP address of one NIC, it will only send out the arp-request from this NIC. So even arp-proxy in this case, it will cause any issue.

            [OCPBUGS-43352] Assisted installer cluster installation fails with IP collision validation, due to a Porxy ARP request.

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !799 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _dd479305869c8866847b14242632c3c5 : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !797 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _5fa19bced9c141a30d2d303172091c9c : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !795 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _bbd3532cb5d2ab4ff79293acb6cedc46 : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !792 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _8b9129a51e76cd28d19da0edf7b14e23 : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !790 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _ebbda33b9da111042eb7befe184a4d3d : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !788 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _17f5dff04c0b4d7b91eebf5be974d40f : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !787 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _5b97f88cb9e48ac05792b1d184ad0b28 : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !786 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _5ad7ad133c8fd02e988f3364473532f1 : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !784 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _032ac6a512e4632c79c7ad909978379a : Updated 3 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !758 of rh-ecosystem-edge / assisted-installer / assisted installer projects on branch rhai-1.0-rhel-8_ upstream _f5a6bd1fa0ddbf58d4739e6c6d225c3a : Updated 3 upstream sources

              eifrach@redhat.com Eran Ifrach
              rhn-support-sar Santhiya R
              Benny Kopilov Benny Kopilov
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: