Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-21750

over 4096 resubmit actions on bridge br-int in ovs logs leading to VM outage

XMLWordPrintable

    • Bug Tracking
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-connectivity-neutron
    • None
    • Hide
      .Unreachable instances on provider networks with a large number of routers
      In RHOSP 17.1 versions, instances on a provider network can be unreachable, in which neither ping or arping work. This has been reported in environments that contain a large number of Networking service (neutron) virtual routers, 200 or more, connected to the provider network.
      *Workaround:* make a change to the RHOSP configuration by following the steps documented in this Knowledge Base Solution: https://access.redhat.com/solutions/7077367.

      Show
      .Unreachable instances on provider networks with a large number of routers In RHOSP 17.1 versions, instances on a provider network can be unreachable, in which neither ping or arping work. This has been reported in environments that contain a large number of Networking service (neutron) virtual routers, 200 or more, connected to the provider network. *Workaround:* make a change to the RHOSP configuration by following the steps documented in this Knowledge Base Solution: https://access.redhat.com/solutions/7077367 .
    • Known Issue
    • Proposed
    • Critical
    • Customer Scenario Regression, External User Impacted

      There is similar bug available in 17.1.3 https://bugzilla.redhat.com/show_bug.cgi?id=2294876Ā 

      which was supposed to be fixed in latest releases of 17.1 but looks like issue is resurfaces in 17.1.11

      Ā 

              grakausk@redhat.com Greg Rakauskas
              schhabdi@redhat.com Shailesh Chhabdiya
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: