Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-6114

Impact statement request for OCPBUGS-57179 OCP4.18.15 - Stale SNATs/LRPs due to failed sync to add metadata after upgrade

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Impact statement for the OCPBUGS-57179 series:

      Which 4.y.z to 4.y'.z' updates increase vulnerability?

      • any to 4.18.z

      Which types of clusters?

      • A cluster gets impacted if it has assigned EgressIPs which can be verified by the PromQL query on the cluster count(ovnkube_clustermanager_num_egress_ips) > 0

      What is the impact? Is it serious enough to warrant removing update recommendations?

      • EgressIP functionality may fail if a pod IP is reused

      How involved is remediation?

      • SSH into each Node and run a command to either clear all the databases or clear the OVN constructs that are causing the issue. We recommend detection then flushing the OVN DBs. SeeĀ https://access.redhat.com/solutions/7125049 for details.

      Is this a regression?

      • yes

              mkennell@redhat.com Martin Kennelly
              hongkliu Hongkai Liu
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: