Regression in NSX op status synchronization logic
Bug #1283856 reported by
Salvatore Orlando
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
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.
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
The issue was introduced with the router db mappings patch (b70dce2), and it affected routers only.
A patch will be pushed soon.