test_bfd_add_may_exist_no_change can fail due to OVN changing the 'status' field
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ovsdbapp |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
=======
Failed 1 tests - output below:
=======
ovsdbapp.
-------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/home/
self.
File "/home/
self.
File "/home/
raise mismatch_error
testtools.
reference = BFD(uuid=
This happens because the 'status' field can be set by OVN, so we can't rely on it not changing during the test.
I see one occurance in CI:
https:/ /opensearch. logs.openstack. org/_dashboards /app/discover/ ?security_ tenant= global# /?_g=(filters: !(),refreshInte rval:(pause: !t,value: 0),time: (from:now- 30d,to: now))&_ a=(columns: !(build_ name,build_ change) ,filters: !(),index: '94869730- aea8-11ec- 9e6a-83741af3fd cd',interval: auto,query: (language: kuery,query: 'message: %22line% 202587, %20in%20test_ bfd_add_ may_exist_ no_change% 22'),sort: !())