Build 2715 : Traceflow timing out when dst netwok of a flow is _UNKNOWN_
Bug #1550387 reported by
Ankit Jain
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
Fix Committed
|
Undecided
|
VishnuVardhan V | ||
| R3.0 |
Fix Committed
|
Undecided
|
VishnuVardhan V | ||
Bug Description
We are showing some flows in the UI with dst vn as __UNKNOWN_. When trace flow is tired on those flows
it times out throwing the error "Error Timeout in fetching details"
Please decide how this should be handled. Screenshot attached
Revision history for this message
| Ankit Jain (ankitja) wrote | #1 |
| Changed in juniperopenstack: | |
| assignee: | Rahul (rahuls) → VishnuVardhan V (vishnuvv) |
| tags: | removed: blocker |
Revision history for this message
| VishnuVardhan V (vishnuvv) wrote | #2 |
| Changed in juniperopenstack: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Flows with unknown as source and destination networks can't be traced, for usability we added the filter in trace flow and map flow grids, where user can filter out the unknown network values.