Hello,

Our integration tests noticed that after a restart, an IP address assigned
to a bridge, is lost from the interface after OVS is restarted. This
appears to be new in 2.15.0. Is it intended for any IP address assigned to
be retained? I did start with a clean OVSDB (re upgrade note in the 2.15.0
release notes).

====<2.15.0>====
root@fogbank:/scratch/openvswitch-2.15.0# ovs-vsctl show
ed2ea5b4-44b3-434f-8d5a-1350424a7bcb
    ovs_version: "2.15.0"
root@fogbank:/scratch/openvswitch-2.15.0# ovs-vsctl add-br testbr
root@fogbank:/scratch/openvswitch-2.15.0# ifconfig testbr 10.10.0.1/24 up
root@fogbank:/scratch/openvswitch-2.15.0# ifconfig testbr
testbr: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.0.1  netmask 255.255.255.0  broadcast 10.10.0.255
        inet6 fe80::481b:b1ff:feda:6047  prefixlen 64  scopeid 0x20<link>
        ether 4a:1b:b1:da:60:47  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7  bytes 586 (586.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@fogbank:/scratch/openvswitch-2.15.0#
/usr/local/share/openvswitch/scripts/ovs-ctl restart
 * Saving flows
 * Exiting ovsdb-server (380677)
 * Starting ovsdb-server
 * system ID not configured, please use --system-id
 * Configuring Open vSwitch system IDs
 * Exiting ovs-vswitchd (380707)
 * Starting ovs-vswitchd
ovs-ofctl: testbr is not a bridge or a socket
ovs-ofctl: testbr is not a bridge or a socket
ovs-ofctl: testbr is not a bridge or a socket
 * Restoring saved flows
 * Enabling remote OVSDB managers
root@fogbank:/scratch/openvswitch-2.15.0# ifconfig testbr
testbr: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 4a:1b:b1:da:60:47  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

====<2.14.2>====
root@fogbank:/scratch/openvswitch-2.14.2# ovs-vsctl show
0fc0bc01-0eec-4811-bb4d-b419c343c166
    ovs_version: "2.14.2"
root@fogbank:/scratch/openvswitch-2.14.2#  ovs-vsctl add-br testbr
root@fogbank:/scratch/openvswitch-2.14.2# ifconfig testbr 10.10.0.1/24 up
root@fogbank:/scratch/openvswitch-2.14.2# ifconfig testbr
testbr: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.0.1  netmask 255.255.255.0  broadcast 10.10.0.255
        inet6 fe80::890:ffff:fe31:664f  prefixlen 64  scopeid 0x20<link>
        ether 0a:90:ff:31:66:4f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6  bytes 516 (516.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@fogbank:/scratch/openvswitch-2.14.2#
/usr/local/share/openvswitch/scripts/ovs-ctl restart
 * Saving flows
 * Exiting ovsdb-server (395391)
 * Starting ovsdb-server
 * system ID not configured, please use --system-id
 * Configuring Open vSwitch system IDs
 * Exiting ovs-vswitchd (395412)
 * Starting ovs-vswitchd
 * Restoring saved flows
 * Enabling remote OVSDB managers
root@fogbank:/scratch/openvswitch-2.14.2#  ifconfig testbr
testbr: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.0.1  netmask 255.255.255.0  broadcast 10.10.0.255
        inet6 fe80::890:ffff:fe31:664f  prefixlen 64  scopeid 0x20<link>
        ether 0a:90:ff:31:66:4f  txqueuelen 1000  (Ethernet)
        RX packets 1  bytes 0 (0.0 B)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 8  bytes 656 (656.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to