[VOL-1946] Transaction id should be unique in grpc metadata requests from af-router - OpenCORD JIRA

XML

Word

Printable

Details

Type: Bug
Status: Resolved (View Workflow)
Priority: Medium
Resolution: Fixed
Affects Version/s: VOLTHA v2.1
Fix Version/s: VOLTHA v2.1
Component/s: api-server
Labels:
None
Environment:

kind-voltha with SKIP_RESTART_API=n where afrouter is restarted.

Create device randomly fails with "transaction-not-acquired" as both core fail to acquire transaction seeing last/stale value in etcd while trying to reserve.

Story Points:
2

Description

The api-server currently allocates a running transaction id starting from 0.

While this is fine, its not safe against api-server restarts when the same txn ids could be reused and etcd Reserve from core can fail for those txn-ids when it sees stale value from last txn id before api-server restarted.

Using uuid as txn id should ensure its unique and safe against restarts.