Node ordering in service chain spec is not preserved at the time service chain instance creation and deletion
Bug #1534061 reported by
vks1
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
Create a service chain spec with Node A and Node B, where the intent is Node B should be behind Node A. For eg.
Node A - VPN
Node B - Loadbalancer
The gbp drivers gets request in random fashion irrespective of the ordering of nodes which means some time VPN gets first instantiated and some time Loabalancer gets initiated first, as per the example.
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in group-based-policy: | |
| status: | New → Incomplete |
To post a comment you must log in.
Waiting for more information from Vikash on this.