[GBP-163] Neutron: controller not getting other-config aug for devstack-compute Created: 18/Jun/15 Updated: 19/Oct/17 Resolved: 31/Aug/15 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | DSLMapping:Neutron |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Keith Burns | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3803 |
| Priority: | High |
| Description |
|
Have seen that due to compute coming up faster than control, ODL controller doesn't seem to get augmentation for other-config. WORKAROUND: del-manager/set-manager after stack. POTENTIAL FIX: once controller up, neutron OVSDB should read OVSDB.topology for this information. |
| Comments |
| Comment by Peter Palmar [ 31/Aug/15 ] |
|
The bug is not reproducible. Verified with
When performing different sequences of the requests vagrant up <node-name> for the gbp-devstack demo's nodes (devstack-control and devstack-compute-1), the required/expected items are part of an OvsdbNodeAugmentation received by NodeDataChangeListener.onDataChanged. An example: getOpenvswitchOtherConfigs=[OpenvswitchOtherConfigs{getOtherConfigKey=local_ip, getOtherConfigValue=192.168.50.20, augmentations={}}, |