On Thu, Nov 12, 2020 at 11:08 AM Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Wed, Nov 11, 2020 at 10:01 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>> NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I
>> noticed that the OVN config was not retained and I had to run on hosts:
>>
>> [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt
>> Using default PKI files
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
>> /usr/lib/systemd/system/openvswitch.service.
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
>> /usr/lib/systemd/system/ovn-controller.service.
>> [root@ov200 ~]#
>>
>> Now it seems the problem persists...
>> Why do I have to run each time?
>>
>> Gianluca
>>
>
> In the mean time I confirm that the manual step below on ov301 let me saw
> it again between the chassis of OVN southbound on engine and I was able to
> migrate VMs to update the other host and then for example to successfully
> ping between VMs on OVN across the two hosts:
>
> [root@ov301 vdsm]# vdsm-tool ovn-config 10.4.192.43 10.4.192.34
> Using default PKI files
> Created symlink
> /etc/systemd/system/multi-user.target.wants/openvswitch.service →
> /usr/lib/systemd/system/openvswitch.service.
> Created symlink
> /etc/systemd/system/multi-user.target.wants/ovn-controller.service →
> /usr/lib/systemd/system/ovn-controller.service.
> [root@ov301 vdsm]#
>
>
As this OVN related problem seems often impacting me, I created this
bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1910340

Thanks for watching
Gianluca
_______________________________________________
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/QNC3ILLHR6YKW7UYRXNRWH3673SUYB4S/

Reply via email to