On 03/08/17 13:59, fukaige wrote: > Hi all: > > Recently, I met a confusing problem when using ovs-2.5.2. When a device fail > to be attach to ovs bridge, I still can get > the port using “ovs-vsctl show”. > > As I see it, we should remove the port’s configuration in ovsdb when failed > to attach it to ovs bridge. Then, we cannot > get the port using “ovs-vsctl show”. > > Could anyone tell me why it is not delete in ovsdb? If it is designed to do > like this or we miss the step to remove the > port’s configuration. > > > > Here is the log: > > > > EulerOS:~ # ovs-vsctl add-br br-test tap01 > > ovs-vsctl: 'add-br' command takes exactly 1 or 3 arguments > > EulerOS:~ # ovs-vsctl add-port br-test tap01 > > ovs-vsctl: Error detected while setting up 'tap01'. See ovs-vswitchd log for > details. > > EulerOS:~ # ovs-vsctl show > > 4a8ab521-ded1-45c7-afb7-04005c05908e > > Bridge br-test > > Port "tap01" > > Interface "tap01" > > Port br-test > > Interface br-test > > type: internal > > ovs_version: "2.5.2" > > > > ovs version: 2ba45f0 odp-util: Fix generating various ct fields in > odp_key_to_dp_packet() > > > > Thanks, > > Kaige Fu > > > > > > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >
The port could not exist yet (e.g a VM which hasn't started yet), but you may want to already configure it. When the VM then later is started and the port is created, it will be already configured and can be used immediately. BR Matthias _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
