[ovirt-users] Re: OVN Geneve tunnels not been established
Hi Dominic That fixed it. VMs have full connectivity and I don't see any errors on the nodes ovn controller. Thanks for the help and quick responses, I really appreciate it. In summary for future reference: If certificate errors are met need to review: ovs-vsctl --no-wait get open . external-ids:ovn-remote ovs-vsctl --no-wait get open . external-ids:ovn-encap-type ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip The ovn-remote will state if the OVN connection is using TCP or TLS. We then do: ovn-nbctl get-ssl ovn-nbctl get-connection ovn-sbctl get-ssl ovn-sbctl get-connection ls -l /etc/pki/ovirt-engine/keys/ovn-* As to check the ovn northbound and southbound configuration and listening ports and if TCP or TLS is used. If tls is used we must update the nodes with: ovn-nbctl set-ssl "ovn northbound interface certificate key" "ovn northbound interface certificate file" ovn-nbctl set-connection pssl:6641 ovn-sbctl set-ssl "ovn southbound interface certificate key" "ovn southbound interface certificate file" ovn-sbctl set-connection pssl:6642 The certificates must reside within nodes through the VDSM client. Finally, we check that all tunnels are established and working ok. If we get to a stuck chassis we simply stop the ovn service on the node and delete the chassis from the northbound interface through: ovn-sbctl chassis-del "chassis_ID" Thank you Best Regards Konstantinos Betsis On Tue, Oct 6, 2020 at 11:37 AM Dominik Holler wrote: > > > On Tue, Oct 6, 2020 at 10:31 AM Konstantinos Betsis > wrote: > >> Hi guys >> >> Sorry to disturb you but i am pretty much stuck at this point with the >> ovn southbound interface. >> >> Is there a way i can flush it and have it reconfigured from ovirt? >> >> > Can you please delete the chassis via > > ovn-sbctl chassis-del 32cd0eb4-d763-4036-bbc9-a4d3a4013ee6 > > while 32cd0eb4-d763-4036-bbc9-a4d3a4013ee6 should be replaced with the id > of the suspicious chassis show by > ovn-sbctl show > > The ovn-controller will add the chassis again in a few seconds, but I hope > that this would remove the inconsistency in the db. > > > >> Thank you >> Best Regards >> Konstantinos Betsis >> >> On Thu, Oct 1, 2020 at 6:52 PM Konstantinos Betsis >> wrote: >> >>> Regarding the ovn-controller logs >>> >>> 2020-10-01T15:51:03.156Z|14143|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.220Z|14144|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.284Z|14145|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.347Z|14146|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.411Z|14147|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.474Z|14148|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.538Z|14149|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.601Z|14150|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.664Z|14151|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:03.727Z|14152|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:08.792Z|14153|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:08.855Z|14154|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:08.919Z|14155|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:08.982Z|14156|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:09.046Z|14157|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:09.109Z|14158|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:09.173Z|14159|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:09.236Z|14160|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> 2020-10-01T15:51:09.299Z|14161|main|INFO|OVNSB commit failed, force >>> recompute next time. >>> >>> >>> I don't think we can see anything more from these. >>> >>> >>> >>> On Thu, Oct 1, 2020 at 6:12 PM Konstantinos Betsis >>> wrote: >>> >>>> Hi Dimitru >>>> >>>> I've seen that
[ovirt-users] Re: OVN Geneve tunnels not been established
Hi guys
Sorry to disturb you but i am pretty much stuck at this point with the ovn
southbound interface.
Is there a way i can flush it and have it reconfigured from ovirt?
Thank you
Best Regards
Konstantinos Betsis
On Thu, Oct 1, 2020 at 6:52 PM Konstantinos Betsis
wrote:
> Regarding the ovn-controller logs
>
> 2020-10-01T15:51:03.156Z|14143|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.220Z|14144|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.284Z|14145|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.347Z|14146|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.411Z|14147|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.474Z|14148|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.538Z|14149|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.601Z|14150|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.664Z|14151|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:03.727Z|14152|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:08.792Z|14153|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:08.855Z|14154|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:08.919Z|14155|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:08.982Z|14156|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:09.046Z|14157|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:09.109Z|14158|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:09.173Z|14159|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:09.236Z|14160|main|INFO|OVNSB commit failed, force
> recompute next time.
> 2020-10-01T15:51:09.299Z|14161|main|INFO|OVNSB commit failed, force
> recompute next time.
>
>
> I don't think we can see anything more from these.
>
>
>
> On Thu, Oct 1, 2020 at 6:12 PM Konstantinos Betsis
> wrote:
>
>> Hi Dimitru
>>
>> I've seen that as well.
>> I've deleted the dc01-node2 (ams03-hypersec02) from ovirt.
>> I've also issued ovs-vsctl emer-reset.
>>
>> But ovn-sbctl list chassis still depicts the node twice.
>> The ovs-sbctl show still depicts 3 geneve tunnels from dc01-node2
>>
>> How, can we fix this?
>>
>> On Thu, Oct 1, 2020 at 9: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 <
>>> k.bet...@gmail.com
>>> > <mailto:k.bet...@gmail.com>> wrote:
>>> >
>>> > Sure
>>> >
>>> > I've attached it for easier reference.
>>> >
>>> > On Wed, Sep 30, 2020 at 2:21 PM Dominik Holler >> > <mailto:dhol...@redhat.com>> wrote:
>>> >
>>> >
>>> >
>>> > On Wed, Sep 30, 2020 at 1:16 PM Konstantinos Betsis
>>> > mailto:k.bet...@gmail.com>>
[ovirt-users] Re: OVN Geneve tunnels not been established
Regarding the ovn-controller logs
2020-10-01T15:51:03.156Z|14143|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.220Z|14144|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.284Z|14145|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.347Z|14146|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.411Z|14147|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.474Z|14148|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.538Z|14149|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.601Z|14150|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.664Z|14151|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:03.727Z|14152|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:08.792Z|14153|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:08.855Z|14154|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:08.919Z|14155|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:08.982Z|14156|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:09.046Z|14157|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:09.109Z|14158|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:09.173Z|14159|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:09.236Z|14160|main|INFO|OVNSB commit failed, force
recompute next time.
2020-10-01T15:51:09.299Z|14161|main|INFO|OVNSB commit failed, force
recompute next time.
I don't think we can see anything more from these.
On Thu, Oct 1, 2020 at 6:12 PM Konstantinos Betsis
wrote:
> Hi Dimitru
>
> I've seen that as well.
> I've deleted the dc01-node2 (ams03-hypersec02) from ovirt.
> I've also issued ovs-vsctl emer-reset.
>
> But ovn-sbctl list chassis still depicts the node twice.
> The ovs-sbctl show still depicts 3 geneve tunnels from dc01-node2
>
> How, can we fix this?
>
> On Thu, Oct 1, 2020 at 9: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 > > <mailto:k.bet...@gmail.com>> wrote:
>> >
>> > Sure
>> >
>> > I've attached it for easier reference.
>> >
>> > On Wed, Sep 30, 2020 at 2:21 PM Dominik Holler > > <mailto:dhol...@redhat.com>> wrote:
>> >
>> >
>> >
>> > On Wed, Sep 30, 2020 at 1:16 PM Konstantinos Betsis
>> > mailto:k.bet...@gmail.com>> 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
[ovirt-users] Re: OVN Geneve tunnels not been established
Hi Dimitru
I've seen that as well.
I've deleted the dc01-node2 (ams03-hypersec02) from ovirt.
I've also issued ovs-vsctl emer-reset.
But ovn-sbctl list chassis still depicts the node twice.
The ovs-sbctl show still depicts 3 geneve tunnels from dc01-node2
How, can we fix this?
On Thu, Oct 1, 2020 at 9: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 > <mailto:k.bet...@gmail.com>> wrote:
> >
> > Sure
> >
> > I've attached it for easier reference.
> >
> > On Wed, Sep 30, 2020 at 2:21 PM Dominik Holler > <mailto:dhol...@redhat.com>> wrote:
> >
> >
> >
> > On Wed, Sep 30, 2020 at 1:16 PM Konstantinos Betsis
> > mailto:k.bet...@gmail.com>> 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
>
> Thanks,
> Dumitru
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
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/users@ovirt.org/message/FQLPZ67LSGRAJ5LC6INRZG2YM64BJFYC/
[ovirt-users] Re: OVN Geneve tunnels not been established
So a new test-net was created under DC01 and was depicted in the networks tab under both DC01 and DC02. I believe for some reason networks are duplicated in DCs, maybe for future use??? Don't know. If one tries to delete the network from the other DC it gets an error, while if deleted from the once initially created it gets deleted from both. >From the DC01-node02 i get the following errors: 2020-09-15T16:48:49.904Z|22748|main|INFO|OVNSB commit failed, force recompute next time. 2020-09-15T16:48:49.905Z|22749|binding|INFO|Claiming lport 9a6cc189-0934-4468-97ae-09f90fa4598d for this chassis. 2020-09-15T16:48:49.905Z|22750|binding|INFO|9a6cc189-0934-4468-97ae-09f90fa4598d: Claiming 56:6f:77:61:00:06 2020-09-15T16:48:49.905Z|22751|binding|INFO|Claiming lport 16162721-c815-4cd8-ab57-f22e6e482c7f for this chassis. 2020-09-15T16:48:49.905Z|22752|binding|INFO|16162721-c815-4cd8-ab57-f22e6e482c7f: Claiming 56:6f:77:61:00:03 2020-09-15T16:48:49.905Z|22753|binding|INFO|Claiming lport b88de6e4-6d77-4e42-b734-4cc676728910 for this chassis. 2020-09-15T16:48:49.905Z|22754|binding|INFO|b88de6e4-6d77-4e42-b734-4cc676728910: Claiming 56:6f:77:61:00:15 2020-09-15T16:48:49.905Z|22755|binding|INFO|Claiming lport b7ff5f2b-4bb4-4250-8ad8-8a7e19d2b4c7 for this chassis. 2020-09-15T16:48:49.905Z|22756|binding|INFO|b7ff5f2b-4bb4-4250-8ad8-8a7e19d2b4c7: Claiming 56:6f:77:61:00:0d 2020-09-15T16:48:49.905Z|22757|binding|INFO|Claiming lport 5d03a7a5-82a1-40f9-b50c-353a26167fa3 for this chassis. 2020-09-15T16:48:49.905Z|22758|binding|INFO|5d03a7a5-82a1-40f9-b50c-353a26167fa3: Claiming 56:6f:77:61:00:02 2020-09-15T16:48:49.905Z|22759|binding|INFO|Claiming lport 12d829c3-64eb-44bc-a0bd-d7219991f35f for this chassis. 2020-09-15T16:48:49.905Z|22760|binding|INFO|12d829c3-64eb-44bc-a0bd-d7219991f35f: Claiming 56:6f:77:61:00:1c 2020-09-15T16:48:49.959Z|22761|main|INFO|OVNSB commit failed, force recompute next time. 2020-09-15T16:48:49.960Z|22762|binding|INFO|Claiming lport 9a6cc189-0934-4468-97ae-09f90fa4598d for this chassis. 2020-09-15T16:48:49.960Z|22763|binding|INFO|9a6cc189-0934-4468-97ae-09f90fa4598d: Claiming 56:6f:77:61:00:06 2020-09-15T16:48:49.960Z|22764|binding|INFO|Claiming lport 16162721-c815-4cd8-ab57-f22e6e482c7f for this chassis. 2020-09-15T16:48:49.960Z|22765|binding|INFO|16162721-c815-4cd8-ab57-f22e6e482c7f: Claiming 56:6f:77:61:00:03 2020-09-15T16:48:49.960Z|22766|binding|INFO|Claiming lport b88de6e4-6d77-4e42-b734-4cc676728910 for this chassis. 2020-09-15T16:48:49.960Z|22767|binding|INFO|b88de6e4-6d77-4e42-b734-4cc676728910: Claiming 56:6f:77:61:00:15 2020-09-15T16:48:49.960Z|22768|binding|INFO|Claiming lport b7ff5f2b-4bb4-4250-8ad8-8a7e19d2b4c7 for this chassis. 2020-09-15T16:48:49.960Z|22769|binding|INFO|b7ff5f2b-4bb4-4250-8ad8-8a7e19d2b4c7: Claiming 56:6f:77:61:00:0d 2020-09-15T16:48:49.960Z|22770|binding|INFO|Claiming lport 5d03a7a5-82a1-40f9-b50c-353a26167fa3 for this chassis. 2020-09-15T16:48:49.960Z|22771|binding|INFO|5d03a7a5-82a1-40f9-b50c-353a26167fa3: Claiming 56:6f:77:61:00:02 2020-09-15T16:48:49.960Z|22772|binding|INFO|Claiming lport 12d829c3-64eb-44bc-a0bd-d7219991f35f for this chassis. 2020-09-15T16:48:49.960Z|22773|binding|INFO|12d829c3-64eb-44bc-a0bd-d7219991f35f: Claiming 56:6f:77:61:00:1c And this repeats forever. The connections to ovn-sbctl is ok and the geneve tunnels are depicted under ovs-vsctl ok. VMs still not able to ping each other. On Tue, Sep 15, 2020 at 7:22 PM Dominik Holler wrote: > > > On Tue, Sep 15, 2020 at 6:18 PM Konstantinos Betsis > wrote: > >> Hi Dominik >> >> Fixed the issue. >> > > Thanks. > > >> I believe the /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf >> needed update also. >> The package is upgraded to the latest version. >> >> Once the provider was updated with the following it functioned perfectly: >> >> Name: ovirt-provider-ovn >> Description: oVirt network provider for OVN >> Type: External Network Provider >> Network Plugin: oVirt Network Provider for OVN >> Automatic Synchronization: Checked >> Unmanaged: Unchecked >> Provider URL: https:dc02-ovirt01.testdomain.com:9696 >> Requires Authentication: Checked >> Username: admin@internal >> Password: "The admin password" >> Protocol: HTTPS >> Host Name: dc02-ovirt01.testdomain.com >> API Port: 35357 >> API Version: v2.0 >> Tenant Name: "Empty" >> >> For some reason the TLS certificate was in conflict with the ovn provider >> details, i would bet the "host" entry. >> >> So now geneve tunnels are established. >> OVN provider is working. >> >> But VMs still do not communicated on the same VM network spanning >> different hosts. >> >> So if we have a VM network test-net on both dc01-host01 and dc01-host02 >> and each host
[ovirt-users] Re: OVN Geneve tunnels not been established
Hi Dominik Fixed the issue. I believe the /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf needed update also. The package is upgraded to the latest version. Once the provider was updated with the following it functioned perfectly: Name: ovirt-provider-ovn Description: oVirt network provider for OVN Type: External Network Provider Network Plugin: oVirt Network Provider for OVN Automatic Synchronization: Checked Unmanaged: Unchecked Provider URL: https:dc02-ovirt01.testdomain.com:9696 Requires Authentication: Checked Username: admin@internal Password: "The admin password" Protocol: HTTPS Host Name: dc02-ovirt01.testdomain.com API Port: 35357 API Version: v2.0 Tenant Name: "Empty" For some reason the TLS certificate was in conflict with the ovn provider details, i would bet the "host" entry. So now geneve tunnels are established. OVN provider is working. But VMs still do not communicated on the same VM network spanning different hosts. So if we have a VM network test-net on both dc01-host01 and dc01-host02 and each host has a VM with IP addresses on the same network, VMs on the same VM network should communicate directly. But traffic does not reach each other. On Tue, Sep 15, 2020 at 7:07 PM Dominik Holler wrote: > Can you try again with: > > [OVN REMOTE] > ovn-remote=ssl:127.0.0.1:6641 > [SSL] > https-enabled=false > ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem > ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer > ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass > [OVIRT] > ovirt-sso-client-secret=*random_test* > ovirt-host=https://dc02-ovirt01.testdomain.com:443 > <https://dc02-ovirt01.testdomain.com/> > ovirt-sso-client-id=ovirt-provider-ovn > ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem > [NETWORK] > port-security-enabled-default=True > [PROVIDER] > > provider-host=dc02-ovirt01.testdomain.com > > > > Please note that the should match the HTTP or HTTPS in the of the > ovirt-prover-ovn configuration in oVirt Engine. > So if the ovirt-provider-ovn entity in Engine is on HTTP, the config file > should use > https-enabled=false > > > On Tue, Sep 15, 2020 at 5:56 PM Konstantinos Betsis > wrote: > >> This is the updated one: >> >> # This file is automatically generated by engine-setup. Please do not >> edit manually >> [OVN REMOTE] >> ovn-remote=ssl:127.0.0.1:6641 >> [SSL] >> https-enabled=true >> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >> [OVIRT] >> ovirt-sso-client-secret=*random_text* >> ovirt-host=https://dc02-ovirt01.testdomain.com:443 >> ovirt-sso-client-id=ovirt-provider-ovn >> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem >> [NETWORK] >> port-security-enabled-default=True >> [PROVIDER] >> provider-host=dc02-ovirt01.testdomain.com >> [AUTH] >> auth-plugin=auth.plugins.static_token:NoAuthPlugin >> >> >> However, it still does not connect. >> It prompts for the certificate but then fails and prompts to see the log >> but the ovirt-provider-ovn.log does not list anything. >> >> Yes we've got ovirt for about a year now from about version 4.1 >> >> > This might explain the trouble. Upgrade of ovirt-provider-ovn should work > flawlessly starting from oVirt 4.2. > > >> On Tue, Sep 15, 2020 at 6:44 PM Dominik Holler >> wrote: >> >>> >>> >>> On Tue, Sep 15, 2020 at 5:34 PM Konstantinos Betsis >>> wrote: >>> >>>> There is a file with the below entries >>>> >>> >>> Impressive, do you know when this config file was created and if it was >>> manually modified? >>> Is this an upgrade from oVirt 4.1? >>> >>> >>>> [root@dc02-ovirt01 log]# cat >>>> /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf >>>> # This file is automatically generated by engine-setup. Please do not >>>> edit manually >>>> [OVN REMOTE] >>>> ovn-remote=tcp:127.0.0.1:6641 >>>> [SSL] >>>> https-enabled=false >>>> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >>>> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >>>> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >>>> [OVIRT] >>>> ovirt-sso-client-secret=*random_test* >>>> ovirt-host=https://dc02-ovirt01.testdomain.com:443 >>>> ovirt-sso-client-id=ovirt-provider-ovn >>>
[ovirt-users] Re: OVN Geneve tunnels not been established
This is the updated one: # This file is automatically generated by engine-setup. Please do not edit manually [OVN REMOTE] ovn-remote=ssl:127.0.0.1:6641 [SSL] https-enabled=true ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass [OVIRT] ovirt-sso-client-secret=*random_text* ovirt-host=https://dc02-ovirt01.testdomain.com:443 ovirt-sso-client-id=ovirt-provider-ovn ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem [NETWORK] port-security-enabled-default=True [PROVIDER] provider-host=dc02-ovirt01.testdomain.com [AUTH] auth-plugin=auth.plugins.static_token:NoAuthPlugin However, it still does not connect. It prompts for the certificate but then fails and prompts to see the log but the ovirt-provider-ovn.log does not list anything. Yes we've got ovirt for about a year now from about version 4.1 On Tue, Sep 15, 2020 at 6:44 PM Dominik Holler wrote: > > > On Tue, Sep 15, 2020 at 5:34 PM Konstantinos Betsis > wrote: > >> There is a file with the below entries >> > > Impressive, do you know when this config file was created and if it was > manually modified? > Is this an upgrade from oVirt 4.1? > > >> [root@dc02-ovirt01 log]# cat >> /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf >> # This file is automatically generated by engine-setup. Please do not >> edit manually >> [OVN REMOTE] >> ovn-remote=tcp:127.0.0.1:6641 >> [SSL] >> https-enabled=false >> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >> [OVIRT] >> ovirt-sso-client-secret=*random_test* >> ovirt-host=https://dc02-ovirt01.testdomain.com:443 >> ovirt-sso-client-id=ovirt-provider-ovn >> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem >> [NETWORK] >> port-security-enabled-default=True >> [PROVIDER] >> >> provider-host=dc02-ovirt01.testdomain.com >> >> The only entry missing is the [AUTH] and under [SSL] the https-enabled is >> false. Should I edit this in this file or is this going to break >> everything? >> >> > Changing the file should improve, but better create a backup into another > diretory before modification. > The only required change is > from > ovn-remote=tcp:127.0.0.1:6641 > to > ovn-remote=ssl:127.0.0.1:6641 > > > > >> On Tue, Sep 15, 2020 at 6:27 PM Dominik Holler >> wrote: >> >>> >>> >>> On Tue, Sep 15, 2020 at 5:11 PM Konstantinos Betsis >>> wrote: >>> >>>> Hi Dominik >>>> >>>> That immediately fixed the geneve tunnels between all hosts. >>>> >>>> >>> thanks for the feedback. >>> >>> >>>> However, the ovn provider is not broken. >>>> After fixing the networks we tried to move a VM to the DC01-host01 so >>>> we powered it down and simply configured it to run on dc01-node01. >>>> >>>> While checking the logs on the ovirt engine i noticed the below: >>>> Failed to synchronize networks of Provider ovirt-provider-ovn. >>>> >>>> The ovn-provider configure on the engine is the below: >>>> Name: ovirt-provider-ovn >>>> Description: oVirt network provider for OVN >>>> Type: External Network Provider >>>> Network Plugin: oVirt Network Provider for OVN >>>> Automatic Synchronization: Checked >>>> Unmanaged: Unchecked >>>> Provider URL: http:localhost:9696 >>>> Requires Authentication: Checked >>>> Username: admin@internal >>>> Password: "The admin password" >>>> Protocol: hTTP >>>> Host Name: dc02-ovirt01 >>>> API Port: 35357 >>>> API Version: v2.0 >>>> Tenant Name: "Empty" >>>> >>>> In the past this was deleted by an engineer and recreated as per the >>>> documentation, and it worked. Do we need to update something due to the SSL >>>> on the ovn? >>>> >>>> >>> Is there a file in /etc/ovirt-provider-ovn/conf.d/ ? >>> engine-setup should have created one. >>> If the file is missing, for testing purposes, you can create a >>> file /etc/ovirt-provider-ovn/conf.d/00-setup-ovirt-provider-ovn-test.conf : >>> [PROVIDER] >>> provider-host=REPLACE_WITH_FQDN >>> [SSL] >>> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >>> ssl-key-fil
[ovirt-users] Re: OVN Geneve tunnels not been established
There is a file with the below entries [root@dc02-ovirt01 log]# cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf # This file is automatically generated by engine-setup. Please do not edit manually [OVN REMOTE] ovn-remote=tcp:127.0.0.1:6641 [SSL] https-enabled=false ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass [OVIRT] ovirt-sso-client-secret=*random_test* ovirt-host=https://dc02-ovirt01.testdomain.com:443 ovirt-sso-client-id=ovirt-provider-ovn ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem [NETWORK] port-security-enabled-default=True [PROVIDER] provider-host=dc02-ovirt01.testdomain.com The only entry missing is the [AUTH] and under [SSL] the https-enabled is false. Should I edit this in this file or is this going to break everything? On Tue, Sep 15, 2020 at 6:27 PM Dominik Holler wrote: > > > On Tue, Sep 15, 2020 at 5:11 PM Konstantinos Betsis > wrote: > >> Hi Dominik >> >> That immediately fixed the geneve tunnels between all hosts. >> >> > thanks for the feedback. > > >> However, the ovn provider is not broken. >> After fixing the networks we tried to move a VM to the DC01-host01 so we >> powered it down and simply configured it to run on dc01-node01. >> >> While checking the logs on the ovirt engine i noticed the below: >> Failed to synchronize networks of Provider ovirt-provider-ovn. >> >> The ovn-provider configure on the engine is the below: >> Name: ovirt-provider-ovn >> Description: oVirt network provider for OVN >> Type: External Network Provider >> Network Plugin: oVirt Network Provider for OVN >> Automatic Synchronization: Checked >> Unmanaged: Unchecked >> Provider URL: http:localhost:9696 >> Requires Authentication: Checked >> Username: admin@internal >> Password: "The admin password" >> Protocol: hTTP >> Host Name: dc02-ovirt01 >> API Port: 35357 >> API Version: v2.0 >> Tenant Name: "Empty" >> >> In the past this was deleted by an engineer and recreated as per the >> documentation, and it worked. Do we need to update something due to the SSL >> on the ovn? >> >> > Is there a file in /etc/ovirt-provider-ovn/conf.d/ ? > engine-setup should have created one. > If the file is missing, for testing purposes, you can create a > file /etc/ovirt-provider-ovn/conf.d/00-setup-ovirt-provider-ovn-test.conf : > [PROVIDER] > provider-host=REPLACE_WITH_FQDN > [SSL] > ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer > ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass > ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem > https-enabled=true > [OVN REMOTE] > ovn-remote=ssl:127.0.0.1:6641 > [AUTH] > auth-plugin=auth.plugins.static_token:NoAuthPlugin > [NETWORK] > port-security-enabled-default=True > > and restart the ovirt-provider-ovn service. > > > > >> From the ovn-provider logs the below is generated after a service restart >> and when the start VM is triggered >> >> 2020-09-15 15:07:33,579 root Starting server >> 2020-09-15 15:07:33,579 root Version: 1.2.29-1 >> 2020-09-15 15:07:33,579 root Build date: 20191217125241 >> 2020-09-15 15:07:33,579 root Githash: cb5a80d >> 2020-09-15 15:08:26,582 root From: :::127.0.0.1:59980 Request: GET >> /v2.0/ports >> 2020-09-15 15:08:26,582 root Could not retrieve schema from tcp: >> 127.0.0.1:6641: Unknown error -1 >> Traceback (most recent call last): >> File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line >> 138, in _handle_request >> method, path_parts, content >> File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", >> line 175, in handle_request >> return self.call_response_handler(handler, content, parameters) >> File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 35, in >> call_response_handler >> with NeutronApi() as ovn_north: >> File "/usr/share/ovirt-provider-ovn/neutron/neutron_api.py", line 95, >> in __init__ >> self.ovsidl, self.idl = ovn_connection.connect() >> File "/usr/share/ovirt-provider-ovn/ovn_connection.py", line 46, in >> connect >> ovnconst.OVN_NORTHBOUND >> File >> "/usr/lib/python2.7/site-packages/ovsdbapp/backend/ovs_idl/connection.py", >> line 127, in from_server >> helper = idlutils.get_schema_helper(connection_string, schema_name) >> File >> "/usr/lib/python2.7/site-packages/ovsdbapp/backend/
[ovirt-users] Re: OVN Geneve tunnels not been established
Hi Dominik That immediately fixed the geneve tunnels between all hosts. However, the ovn provider is not broken. After fixing the networks we tried to move a VM to the DC01-host01 so we powered it down and simply configured it to run on dc01-node01. While checking the logs on the ovirt engine i noticed the below: Failed to synchronize networks of Provider ovirt-provider-ovn. The ovn-provider configure on the engine is the below: Name: ovirt-provider-ovn Description: oVirt network provider for OVN Type: External Network Provider Network Plugin: oVirt Network Provider for OVN Automatic Synchronization: Checked Unmanaged: Unchecked Provider URL: http:localhost:9696 Requires Authentication: Checked Username: admin@internal Password: "The admin password" Protocol: hTTP Host Name: dc02-ovirt01 API Port: 35357 API Version: v2.0 Tenant Name: "Empty" In the past this was deleted by an engineer and recreated as per the documentation, and it worked. Do we need to update something due to the SSL on the ovn? >From the ovn-provider logs the below is generated after a service restart and when the start VM is triggered 2020-09-15 15:07:33,579 root Starting server 2020-09-15 15:07:33,579 root Version: 1.2.29-1 2020-09-15 15:07:33,579 root Build date: 20191217125241 2020-09-15 15:07:33,579 root Githash: cb5a80d 2020-09-15 15:08:26,582 root From: :::127.0.0.1:59980 Request: GET /v2.0/ports 2020-09-15 15:08:26,582 root Could not retrieve schema from tcp: 127.0.0.1:6641: Unknown error -1 Traceback (most recent call last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 138, in _handle_request method, path_parts, content File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, in handle_request return self.call_response_handler(handler, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 35, in call_response_handler with NeutronApi() as ovn_north: File "/usr/share/ovirt-provider-ovn/neutron/neutron_api.py", line 95, in __init__ self.ovsidl, self.idl = ovn_connection.connect() File "/usr/share/ovirt-provider-ovn/ovn_connection.py", line 46, in connect ovnconst.OVN_NORTHBOUND File "/usr/lib/python2.7/site-packages/ovsdbapp/backend/ovs_idl/connection.py", line 127, in from_server helper = idlutils.get_schema_helper(connection_string, schema_name) File "/usr/lib/python2.7/site-packages/ovsdbapp/backend/ovs_idl/idlutils.py", line 128, in get_schema_helper 'err': os.strerror(err)}) Exception: Could not retrieve schema from tcp:127.0.0.1:6641: Unknown error -1 When i update the ovn provider from the GUI to have https://localhost:9696/ and HTTPS as the protocol the test fails. On Tue, Sep 15, 2020 at 5:35 PM Dominik Holler wrote: > > > On Mon, Sep 14, 2020 at 9:25 AM Konstantinos Betsis > wrote: > >> Hi Dominik >> >> When these commands are used on the ovirt-engine host the output is the >> one depicted in your email. >> For your reference see also below: >> >> [root@ath01-ovirt01 certs]# ovn-nbctl get-ssl >> Private key: /etc/pki/ovirt-engine/keys/ovn-ndb.key.nopass >> Certificate: /etc/pki/ovirt-engine/certs/ovn-ndb.cer >> CA Certificate: /etc/pki/ovirt-engine/ca.pem >> Bootstrap: false >> [root@ath01-ovirt01 certs]# ovn-nbctl get-connection >> ptcp:6641 >> >> [root@ath01-ovirt01 certs]# ovn-sbctl get-ssl >> Private key: /etc/pki/ovirt-engine/keys/ovn-sdb.key.nopass >> Certificate: /etc/pki/ovirt-engine/certs/ovn-sdb.cer >> CA Certificate: /etc/pki/ovirt-engine/ca.pem >> Bootstrap: false >> [root@ath01-ovirt01 certs]# ovn-sbctl get-connection >> read-write role="" ptcp:6642 >> >> > ^^^ the line above points to the problem: ovn-central is configured to use > plain TCP without ssl. > engine-setup usually configures ovn-central to use SSL. That the files > /etc/pki/ovirt-engine/keys/ovn-* exist, shows, > that engine-setup was triggered correctly. Looks like the ovn db was > dropped somehow, this should not happen. > This can be fixed manually by executing the following commands on engine's > machine: > ovn-nbctl set-ssl /etc/pki/ovirt-engine/keys/ovn-ndb.key.nopass > /etc/pki/ovirt-engine/certs/ovn-ndb.cer /etc/pki/ovirt-engine/ca.pem > ovn-nbctl set-connection pssl:6641 > ovn-sbctl set-ssl /etc/pki/ovirt-engine/keys/ovn-sdb.key.nopass > /etc/pki/ovirt-engine/certs/ovn-sdb.cer /etc/pki/ovirt-engine/ca.pem > ovn-sbctl set-connection pssl:6642 > > The /var/log/openvswitch/ovn-controller.log on the hosts should tell that > br-int.mgmt is connected now. > > > >> [root@ath01-ovirt01 certs]# ls -l /etc/pki/ovirt-engine/keys/ovn-* >> -rw-r-. 1 root hugetlbfs 1828 Jun 25 11:08 >
[ovirt-users] Re: OVN Geneve tunnels not been established
ler wrote:
> Looks still like the ovn-controller on the host has problems communicating
> with ovn-southbound.
>
> Are there any hints in /var/log/openvswitch/*.log,
> especially in /var/log/openvswitch/ovsdb-server-sb.log ?
>
> Can you please check the output of
>
> ovn-nbctl get-ssl
> ovn-nbctl get-connection
> ovn-sbctl get-ssl
> ovn-sbctl get-connection
> ls -l /etc/pki/ovirt-engine/keys/ovn-*
>
> it should be similar to
>
> [root@ovirt-43 ~]# ovn-nbctl get-ssl
> Private key: /etc/pki/ovirt-engine/keys/ovn-ndb.key.nopass
> Certificate: /etc/pki/ovirt-engine/certs/ovn-ndb.cer
> CA Certificate: /etc/pki/ovirt-engine/ca.pem
> Bootstrap: false
> [root@ovirt-43 ~]# ovn-nbctl get-connection
> pssl:6641:[::]
> [root@ovirt-43 ~]# ovn-sbctl get-ssl
> Private key: /etc/pki/ovirt-engine/keys/ovn-sdb.key.nopass
> Certificate: /etc/pki/ovirt-engine/certs/ovn-sdb.cer
> CA Certificate: /etc/pki/ovirt-engine/ca.pem
> Bootstrap: false
> [root@ovirt-43 ~]# ovn-sbctl get-connection
> read-write role="" pssl:6642:[::]
> [root@ovirt-43 ~]# ls -l /etc/pki/ovirt-engine/keys/ovn-*
> -rw-r-. 1 root hugetlbfs 1828 Oct 14 2019
> /etc/pki/ovirt-engine/keys/ovn-ndb.key.nopass
> -rw---. 1 root root 2709 Oct 14 2019
> /etc/pki/ovirt-engine/keys/ovn-ndb.p12
> -rw-r-. 1 root hugetlbfs 1828 Oct 14 2019
> /etc/pki/ovirt-engine/keys/ovn-sdb.key.nopass
> -rw---. 1 root root 2709 Oct 14 2019
> /etc/pki/ovirt-engine/keys/ovn-sdb.p12
>
>
>
>
> On Fri, Sep 11, 2020 at 1:10 PM Konstantinos Betsis
> wrote:
>
>> I did a restart of the ovn-controller, this is the output of the
>> ovn-controller.log
>>
>> 2020-09-11T10:54:07.566Z|1|vlog|INFO|opened log file
>> /var/log/openvswitch/ovn-controller.log
>> 2020-09-11T10:54:07.568Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connecting...
>> 2020-09-11T10:54:07.568Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connected
>> 2020-09-11T10:54:07.570Z|4|main|INFO|OVS IDL reconnected, force
>> recompute.
>> 2020-09-11T10:54:07.571Z|5|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connecting...
>> 2020-09-11T10:54:07.571Z|6|main|INFO|OVNSB IDL reconnected, force
>> recompute.
>> 2020-09-11T10:54:07.685Z|7|stream_ssl|WARN|SSL_connect: unexpected
>> SSL connection close
>> 2020-09-11T10:54:07.685Z|8|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connection attempt failed (Protocol error)
>> 2020-09-11T10:54:08.685Z|9|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connecting...
>> 2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected
>> SSL connection close
>> 2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connection attempt failed (Protocol error)
>> 2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> waiting 2 seconds before reconnect
>> 2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connecting...
>> 2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected
>> SSL connection close
>> 2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connection attempt failed (Protocol error)
>> 2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> waiting 4 seconds before reconnect
>> 2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connecting...
>> 2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected
>> SSL connection close
>> 2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> connection attempt failed (Protocol error)
>> 2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
>> continuing to reconnect in the background but suppressing further logging
>>
>>
>> I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP
>> OVIRTMGMT_NETWORK_DC
>> This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can
>> redo it if you wan.
>>
>> After the restart of the ovn-controller the OVIRT ENGINE still shows only
>> two geneve connections one with DC01-host02 and DC02-host01.
>> Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144"
>> hostname: "dc02-host01"
>> Encap geneve
>> ip: "DC02-host01_IP"
>> options: {csum="true"}
>> Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c"
>> hostname: "DC01-host02"
>> Encap geneve
>> ip: "DC01-host02"
>> options: {csum="true"}
>>
>> I'v
[ovirt-users] Re: OVN Geneve tunnels not been established
I did a restart of the ovn-controller, this is the output of the
ovn-controller.log
2020-09-11T10:54:07.566Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovn-controller.log
2020-09-11T10:54:07.568Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2020-09-11T10:54:07.568Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2020-09-11T10:54:07.570Z|4|main|INFO|OVS IDL reconnected, force
recompute.
2020-09-11T10:54:07.571Z|5|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:07.571Z|6|main|INFO|OVNSB IDL reconnected, force
recompute.
2020-09-11T10:54:07.685Z|7|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:07.685Z|8|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:08.685Z|9|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
waiting 2 seconds before reconnect
2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
waiting 4 seconds before reconnect
2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
continuing to reconnect in the background but suppressing further logging
I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP
OVIRTMGMT_NETWORK_DC
This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can
redo it if you wan.
After the restart of the ovn-controller the OVIRT ENGINE still shows only
two geneve connections one with DC01-host02 and DC02-host01.
Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144"
hostname: "dc02-host01"
Encap geneve
ip: "DC02-host01_IP"
options: {csum="true"}
Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c"
hostname: "DC01-host02"
Encap geneve
ip: "DC01-host02"
options: {csum="true"}
I've re-done the vdsm-tool command and nothing changed againwith
the same errors as the systemctl restart ovn-controller
On Fri, Sep 11, 2020 at 1:49 PM Dominik Holler wrote:
> Please include ovirt-users list in your reply, to share the knowledge and
> experience with the community!
>
> On Fri, Sep 11, 2020 at 12:12 PM Konstantinos Betsis
> wrote:
>
>> Ok below the output per node and DC
>> DC01
>> node01
>>
>> [root@dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC01-NODE01*"
>>
>> node02
>>
>> [root@dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC01-NODE02*"
>>
>> DC02
>> node01
>>
>> [root@dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC02-NODE01*"
>>
>>
> Looks good.
>
>
>> DC01 node01 and node02 share the same VM networks and VMs deployed on top
>> of them cannot talk to VM on the other hypervisor.
>>
>
> Maybe there is a hint on ovn-controller.log on dc01-node02 ? Maybe
> restarting ovn-controller creates more helpful log messages?
>
> You can also try restart the ovn configuration on all hosts by executing
> vdsm-tool ovn-config OVIRT_E
