Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-70264

[RFE]: Do not remove external IP attached to the NIC while reapply or bouncing the NIC profile

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • None
    • rhel-net-mgmt
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given an active NetworkManager profile with preserve-external-ips=true,
      When the profile is bounced (nmcli con down/up, device reapply),
      Then VIPs manually added externally are not removed.

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given an active NetworkManager profile with preserve-external-ips=true, When the profile is bounced (nmcli con down/up, device reapply), Then VIPs manually added externally are not removed. ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • All
    • Linux
    • None

      Goal

      We have seen times when IP(basically VIP's) is managed by some external service/script(which NM not aware) like keepalived, oracle,etc, performing "nmcli con down/up" or "nmcli device reapply" causes these external IP(VIP's) to be removed from NIC. This results in connectivity issues.

       

      While I was discussing this in #nm slack channel, I came to know about "https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/gdbus-org.freedesktop.NetworkManager.Device.html#gdbus-method-org-freedesktop-NetworkManager-Device.Reapply"  from Lubomir Rintel.

       

      I think if we can add it in our product it can help for such customers where VIP's are added by some services/script.

      Acceptance criteria

      After  performing "nmcli con down/up" or "nmcli device reapply" , VIP's not managed by NM should remain intact.

              rh-ee-sfaye Stanislas Faye
              prpatel@redhat.com Prijesh Patel
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: