On 10/1/20 8:59 AM, Dumitru Ceara wrote:
> On 9/30/20 3:41 PM, Konstantinos Betsis wrote:
>> From the configuration I can see only three nodes.....
>> "Encap":{
>> #dc01-node02
>> "da8fb1dc-f832-4d62-a01d-2e5aef018c8d":{"ip":"10.137.156.56","chassis_name":"be3abcc9-7358-4040-a37b-8d8a782f239c","options":["map",[["csum","true"]]],"type":"geneve"},
>> #dc01-node01
>> "4808bd8f-7e46-4f29-9a96-046bb580f0c5":{"ip":"10.137.156.55","chassis_name":"95ccb04a-3a08-4a62-8bc0-b8a7a42956f8","options":["map",[["csum","true"]]],"type":"geneve"},
>> #dc02-node01
>> "f20b33ae-5a6b-456c-b9cb-2e4d8b54d8be":{"ip":"192.168.121.164","chassis_name":"c4b23834-aec7-4bf8-8be7-aa94a50a6144","options":["map",[["csum","true"]]],"type":"geneve"}}
>>
>> So I don't understand why the dc01-node02 tries to establish a tunnel
>> with itself.....
>>
>> Is there a way for ovn to refresh according to Ovirt network database as
>> to not affect VM networks?
>>
>> On Wed, Sep 30, 2020 at 2:33 PM Konstantinos Betsis <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Sure
>>
>> I've attached it for easier reference.
>>
>> On Wed, Sep 30, 2020 at 2:21 PM Dominik Holler <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>
>>
>> On Wed, Sep 30, 2020 at 1:16 PM Konstantinos Betsis
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>> Hi Dominik
>>
>> The DC01-node02 was formatted and reinstalled and then
>> attached to ovirt environment.
>> Unfortunately we exhibit the same issue.
>> The new DC01-node02 tries to establish geneve tunnels to his
>> own IP.
>>
>> [root@dc01-node02 ~]# ovs-vsctl show
>> eff2663e-cb10-41b0-93ba-605bb5c7bd78
>> Bridge br-int
>> fail_mode: secure
>> Port "ovn-95ccb0-0"
>> Interface "ovn-95ccb0-0"
>> type: geneve
>> options: {csum="true", key=flow,
>> remote_ip="dc01-node01_IP"}
>> Port "ovn-be3abc-0"
>> Interface "ovn-be3abc-0"
>> type: geneve
>> options: {csum="true", key=flow,
>> remote_ip="dc01-node02_IP"}
>> Port "ovn-c4b238-0"
>> Interface "ovn-c4b238-0"
>> type: geneve
>> options: {csum="true", key=flow,
>> remote_ip="dc02-node01_IP"}
>> Port br-int
>> Interface br-int
>> type: internal
>> ovs_version: "2.11.0"
>>
>>
>> Is there a way to fix this on the Ovirt engine since this is
>> where the information resides?
>> Something is broken there.
>>
>>
>> I suspect that there is an inconsistency in the OVN SB DB.
>> Is there a way to share your /var/lib/openvswitch/ovnsb_db.db
>> with us?
>>
>>
>
> Hi Konstantinos,
>
> One of the things I noticed in the SB DB you attached is that two of the
> chassis records have the same hostname:
>
> $ ovn-sbctl list chassis | grep ams03-hypersec02
> hostname : ams03-hypersec02
> hostname : ams03-hypersec02
>
> This shouldn't be a major issue but shows a potential misconfiguration
> on the nodes. Could you please double check the hostname configuration
> of the nodes?
>
> Would it also be possible to attach the openvswitch conf.db from the
> three nodes? It should be in /var/lib/openvswitch/conf.db
>
Also, it might help pinpoint the issue if we have the ovn-controller
logs from the OVN nodes. They should be in
/var/log/openvswitch/ovn-controller.log
Thanks again,
Dumitru
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/CMVG2VJF3NCJWU54JRJU5KXGWEAEX7HQ/
