yahoo-eng-team team mailing list archive

[Salvatore Orlando <1283856@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

While performing tests on the async status synchronization logic, it
emerged that state changes are not being anymore written to the neutron
database by the sync thread.

The sync thread correctly reads data from the backend but then does not update the status for changed objects.
The regression might have been caused by recent changes in ID mapping logic or by other bug fixes on the sync logic.

Reproduction step:

- Artificially put a NSX resource down, for instance by removing the GW service for a router
- Wait for synchronization
- After synchronization, the status in the DB is not updated.

Punctual state synchronization still works correctly.

** Affects: neutron
     Importance: High
     Assignee: Salvatore Orlando (salvatore-orlando)
         Status: New


** Tags: nicira

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1283856

Title:
  Regression in NSX op status synchronization logic

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  While performing tests on the async status synchronization logic, it
  emerged that state changes are not being anymore written to the
  neutron database by the sync thread.

  The sync thread correctly reads data from the backend but then does not update the status for changed objects.
  The regression might have been caused by recent changes in ID mapping logic or by other bug fixes on the sync logic.

  Reproduction step:

  - Artificially put a NSX resource down, for instance by removing the GW service for a router
  - Wait for synchronization
  - After synchronization, the status in the DB is not updated.

  Punctual state synchronization still works correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1283856/+subscriptions