[GBP-222] GBP sees SF as endpoint Created: 12/Feb/16 Updated: 19/Oct/17 Resolved: 17/Feb/16 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | Endpoint Repository |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Keith Burns | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 5342 |
| Description |
|
This was not happening at 11:30 CET last night, and we have changed nothing. Not sure where the issue is yet, but this has never happened until today. the SF as a neutron port does not meet all the conditions to be an GBP Endpoint, so the fact its continually there, and we get OVSDB notifications continually is worrying. Continuing to triage but at this point, stuff worked, now broken. |
| Comments |
| Comment by Keith Burns [ 12/Feb/16 ] |
|
Attachment karaflogs.zip has been added with description: karaflogs |
| Comment by Martin Sunal [ 12/Feb/16 ] |
| Comment by A H [ 17/Feb/16 ] |
|
Have we been able to verify the fix for this bug? |