functional tests failing due to duplicate Encap entries
Bug #1810292 reported by
Daniel Alvarez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Undecided
|
Daniel Alvarez |
Bug Description
When we create fake chassis from functional tests, a new Encap row is created for ip '172.24.4.10' and type 'geneve'. After this patch [0] merged in OVS, that's considered a constraint violation so our functional tests fail.
It doesn't make sense to have two chassis with the same IP address and encap type but for the purpose of functional tests we can just 'fake' it by using different IP addresses. This shouldn't have any side effect as ovn-controller is not running on functional tests and will allow us to still test multiple chassis scenarios.
Changed in networking-ovn: | |
assignee: | nobody → Daniel Alvarez (dalvarezs) |
tags: | added: networking-ovn-proactive-backport-potential |
tags: | removed: networking-ovn-proactive-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/627961
Review: https:/