Oh, this is OVS 1.4.6. Any reason not to use a newer and still normally supported version of OVS? It's hard to guess at issues with such an old version.
On Thu, Jul 03, 2014 at 09:59:41AM +0100, Joni Lee wrote: > Hi Ben, > > record for the next minute as follows. In some cases the "find Interface" can > return a "ofport" (not empty), so the command "set Port tag" can be performed > after the "add-port" > https://drive.google.com/file/d/0Bw07rcRwQIFydVZYX1hReGZhMU0/edit?usp=sharing > > ? > On the other hand, the openStack folks must implement a failure handling for > the case "ofport" is still empty after "add-port" returned successfully: > https://review.openstack.org/#/c/65838 > > ? > Also I want to remind our current version: > openvswitch: 1.4.6-0ubuntu1.12.04.2~lp1259285 > Linux kernel: 3.2.0-51-generic > > > On Wednesday, July 2, 2014 9:55 PM, Ben Pfaff <b...@nicira.com> wrote: > > > > On Wed, Jul 02, 2014 at 11:05:57AM +0100, Joni Lee wrote: > > > Thank you Ben, > > > > - ovs-vswitchd.log did show that the port was added to br-int: > > > > Jun 30 07:30:14|5422458|bridge|INFO|created port qr-3cc2ad9c-a3 on bridge > > br-int > > > > > > - I only found this "No such device" suspicious. Is this logged by the > > "find Interface" command? (because the command was executed exactly at > > second 15 and returned empty "ofport") > > > > Jun 30 07:30:15|5422579|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on > > qr-3cc2ad9c-a3 device failed: No such device > > > > - In the ovsdb log, the port was added to the db at second 13 successfully. > > But ovsdb log looks like it never records any entries for "ofport" (i guess > > this is normal). > > You showed us one record from the ovsdb log, could you show us the > records after that (for the next minute or so) also? _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss