[Bug 1955578] Re: OVN transaction could not be completed due to a race condition

[Corey Bryant]

** Description changed:

  When executing the test "test_connectivity_through_2_routers" it is highly possible to have
  a race condition:
  
  networking_ovn.common.exceptions.RevisionConflict: OVN revision number
  for {PORT_ID} (type: ports) is equal or higher than the given resource.
  Skipping update.
  
  Bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=1860448
+ 
+ 
+ ===== Ubuntu SRU Details =====
+ [Impact]
+ See bug description.
+ 
+ [Test Case]
+ Deploy openstack with OVN. Run the test_connectivity_through_2_routers test from https://github.com/openstack/neutron-tempest-plugin. This could also be tested manually based on what that test does. Ensure the router port status is not set to DOWN at any point.
+ 
+ [Where problems could occur]
+ The existing bug could still occur if the assumpion that specifying the port type is not correct. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upsream branches.

** Description changed:

  When executing the test "test_connectivity_through_2_routers" it is highly possible to have
  a race condition:
  
  networking_ovn.common.exceptions.RevisionConflict: OVN revision number
  for {PORT_ID} (type: ports) is equal or higher than the given resource.
  Skipping update.
  
  Bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=1860448
  
- 
  ===== Ubuntu SRU Details =====
  [Impact]
  See bug description.
  
  [Test Case]
  Deploy openstack with OVN. Run the test_connectivity_through_2_routers test from https://github.com/openstack/neutron-tempest-plugin. This could also be tested manually based on what that test does. Ensure the router port status is not set to DOWN at any point.
  
  [Where problems could occur]
- The existing bug could still occur if the assumpion that specifying the port type is not correct. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upsream branches.
+ The existing bug could still occur if the assumpion that specifying the port type is not correct. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upstream branches.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1955578

Title:
  OVN transaction could not be completed due to a race condition

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Focal:
  Triaged

Bug description:
  When executing the test "test_connectivity_through_2_routers" it is highly possible to have
  a race condition:

  networking_ovn.common.exceptions.RevisionConflict: OVN revision number
  for {PORT_ID} (type: ports) is equal or higher than the given
  resource. Skipping update.

  Bugzilla reference:
  https://bugzilla.redhat.com/show_bug.cgi?id=1860448

  ===== Ubuntu SRU Details =====
  [Impact]
  See bug description.

  [Test Case]
  Deploy openstack with OVN. Run the test_connectivity_through_2_routers test from https://github.com/openstack/neutron-tempest-plugin. This could also be tested manually based on what that test does. Ensure the router port status is not set to DOWN at any point.

  [Where problems could occur]
  The existing bug could still occur if the assumpion that specifying the port type is not correct. Presumably this is not the case, but that is a theoritical potential for where problems could occur. All of these patches have already landed in the corresponding upstream branches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1955578/+subscriptions