On Mon, Mar 18, 2019 at 2:20 PM Gianluca Cecchi <gianluca.cec...@gmail.com> wrote: > > Hello, > passing from old manual to current OVN in 4.3.1 it seems I have some problems > with OVN now. > I cannot assign network on OVN to VM (powered on or off doesn't change). > When I add//edit a vnic, they are not on the possible choices > Environment composed by three hosts and one engine (external on vSphere). > The mgmt network during time has been configured on network named > ovirtmgmntZ2Z3 > On engine it seems there are 2 switches for every defined ovn network (ovn192 > and ovn172) > Below some output of commands in case any inconsistency has remained and I > can purge it. > Thanks in advance. >
I'm very confused here; you mention that on engine there are 2 switches for every ovn network, but, on your ovn-nbctl list logical_switch output I can clearly see the 2 logical switches where the OVN logical networks are stored. Who created those ? Could you show us the properties of those 2 networks ? (e.g. ovn-nbctl list logical_switch 32367d8a-460f-4447-b35a-abe9ea5187e0 & ovn-nbctl list logical_switch 64c4c17f-cd67-4e29-939e-2b952495159f) +Marcin Mirecki does this ring a bell? AFAIU, the ovn network names had to be unique - until bug [0] was fixed, where the network names would have a whole different format - e.g. ovirt-<network_name>-<generated_uuid> . @Gianluca Cecchi , I notice that one of your duplicate networks - 'ovn192' - has no ports attached. That makes it the perfect candidate to be deleted, and see if it becomes 'listable' on engine. That would help rule out the 'duplicate name' theory. At the moment, I can't think of a better alternative. Let's see if Marcin comes up with a better test / idea / alternative. Also, please let us know the version of the ovirt-provider-ovn, openvswitch-ovn-central, and openvswitch-ovn-host. [0] - https://bugzilla.redhat.com/show_bug.cgi?id=1503577 > Gianluca > > - On manager ovmgr1: > > [root@ovmgr1 ~]# ovs-vsctl show > eae54ff9-b86c-4050-8241-46f44336ba94 > ovs_version: "2.10.1" > [root@ovmgr1 ~]# > > [root@ovmgr1 ~]# ovn-nbctl show > switch 32367d8a-460f-4447-b35a-abe9ea5187e0 (ovn192) > port affc5570-3e5a-439c-9fdf-d75d6810e3a3 > addresses: ["00:1a:4a:17:01:73"] > port f639d541-2118-4c24-b478-b7a586eb170c > addresses: ["00:1a:4a:17:01:75"] > switch 6110649a-db2b-4de7-8fbc-601095cfe510 (ovn192) > switch 64c4c17f-cd67-4e29-939e-2b952495159f (ovn172) > port 32c348d9-12e9-4bcf-a43f-69338c887cfc > addresses: ["00:1a:4a:17:01:72 dynamic"] > port 3c77c2ea-de00-43f9-a5c5-9b3ffea5ec69 > addresses: ["00:1a:4a:17:01:74 dynamic"] > switch 04501f6b-3977-4ba1-9ead-7096768d796d (ovn172) > port 0a2a47bc-ea0d-4f1d-8f49-ec903e519983 > addresses: ["00:1a:4a:17:01:65 dynamic"] > port 8fc7bed4-7663-4903-922b-05e490c6a5a1 > addresses: ["00:1a:4a:17:01:64 dynamic"] > port f2b64f89-b719-484c-ac02-2a1ac8eaacdb > addresses: ["00:1a:4a:17:01:59 dynamic"] > port f7389c88-1ea1-47c2-92fd-6beffb2e2190 > addresses: ["00:1a:4a:17:01:58 dynamic"] > [root@ovmgr1 ~]# > > - On host ov200 (10.4.192.32 on ovirtmgmntZ2Z3): > [root@ov200 ~]# ovs-vsctl show > ae0a1256-7250-46a2-a1b6-8f0ae6105c20 > Bridge br-int > fail_mode: secure > Port br-int > Interface br-int > type: internal > Port "ovn-ddecf0-0" > Interface "ovn-ddecf0-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.33"} > Port "ovn-b8872a-0" > Interface "ovn-b8872a-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.34"} > ovs_version: "2.10.1" > [root@ov200 ~]# > > - On host ov300 (10.4.192.33 on ovirtmgmntZ2Z3): > > [root@ov300 ~]# ovs-vsctl show > f1a41e9c-16fb-4aa2-a386-2f366ade4d3c > Bridge br-int > fail_mode: secure > Port br-int > Interface br-int > type: internal > Port "ovn-b8872a-0" > Interface "ovn-b8872a-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.34"} > Port "ovn-1dce5b-0" > Interface "ovn-1dce5b-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.32"} > ovs_version: "2.10.1" > [root@ov300 ~]# > > - On host ov301 (10.4.192.34 on ovirtmgmntZ2Z3): > [root@ov301 ~]# ovs-vsctl show > 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 > Bridge br-int > fail_mode: secure > Port "ovn-1dce5b-0" > Interface "ovn-1dce5b-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.32"} > Port "ovn-ddecf0-0" > Interface "ovn-ddecf0-0" > type: geneve > options: {csum="true", key=flow, remote_ip="10.4.192.33"} > Port br-int > Interface br-int > type: internal > ovs_version: "2.10.1" > [root@ov301 ~]# > > In web admin gui: > > In network -> networks -> > - ovn192 > Id: 8fd63a10-a2ba-4c56-a8e0-0bc8d70be8b5 > VDSM Name: ovn192 > External ID: 32367d8a-460f-4447-b35a-abe9ea5187e0 > > - ovn172 > Id: 7546d5d3-a0e3-40d5-9d22-cf355da47d3a > VDSM Name: ovn172 > External ID: 64c4c17f-cd67-4e29-939e-2b952495159f > > > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/W6U4XJHNMYMD3WIXDCPGOXLW6DFMCYIM/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4TGVDD7SJSLH5TZG2ML2ZL5RIDKFAEBR/
