Activity log for bug #1852200

Date Who What changed Old value New value Message
2019-11-12 10:44:31 Frode Nordahl bug added bug
2019-11-12 10:57:20 Frode Nordahl description When creating instances you can sometimes see messages like these in the log: 2019-11-12 10:36:22.681 32728 ERROR vif_plug_ovs.ovsdb.impl_vsctl [req-159681cf-ebb2-4844-b86d-8f6e7b8d40f1 ebd65ae223c24c48b31acc8f3235927d 061f59f3ebf944918db16e7a16567074 - fa8df29bb9804ab5aff24fe38536f203 fa8df29bb9804ab5aff24fe38536f203] Unable to execute ['ovs-vsctl', '--timeout=120', '--oneline', '--format=json', '--db=tcp:127.0.0.1:6640', '--', '--may-exist', 'add-br', 'br-int', '--', 'set', 'Bridge', 'br-int', 'datapath_type=system']. Exception: Unexpected error while running command. 2019-11-12 10:37:45.904 32728 ERROR vif_plug_ovs.ovsdb.impl_vsctl [req-fce4021e-f0f7-4c25-bbd6-522ed2225bb7 ebd65ae223c24c48b31acc8f3235927d 061f59f3ebf944918db16e7a16567074 - fa8df29bb9804ab5aff24fe38536f203 fa8df29bb9804ab5aff24fe38536f203] Unable to execute ['ovs-vsctl', '--timeout=120', '--oneline', '--format=json', '--db=tcp:127.0.0.1:6640', '--', '--if-exists', 'del-port', 'br-int', 'tapb205428b-83']. Exception: Unexpected error while running command. Open vSwitch Switch is not configured to listen on a TCP connection by default. Nova's default has recently changed [0]. Perhaps we should point Nova at the Unix socket Open vSwitch listens to? Often instance creation succeeds, but I also see instance creation failures that correlate with the above messages. I have yet to establish any causation between the two events. 0: https://github.com/openstack/os-vif/blob/master/releasenotes/notes/add-ovsdb-native-322fffb49c91503d.yaml When creating instances you can sometimes see messages like these in the log: 2019-11-12 10:36:22.681 32728 ERROR vif_plug_ovs.ovsdb.impl_vsctl [req-159681cf-ebb2-4844-b86d-8f6e7b8d40f1 ebd65ae223c24c48b31acc8f3235927d 061f59f3ebf944918db16e7a16567074 - fa8df29bb9804ab5aff24fe38536f203 fa8df29bb9804ab5aff24fe38536f203] Unable to execute ['ovs-vsctl', '--timeout=120', '--oneline', '--format=json', '--db=tcp:127.0.0.1:6640', '--', '--may-exist', 'add-br', 'br-int', '--', 'set', 'Bridge', 'br-int', 'datapath_type=system']. Exception: Unexpected error while running command. 2019-11-12 10:37:45.904 32728 ERROR vif_plug_ovs.ovsdb.impl_vsctl [req-fce4021e-f0f7-4c25-bbd6-522ed2225bb7 ebd65ae223c24c48b31acc8f3235927d 061f59f3ebf944918db16e7a16567074 - fa8df29bb9804ab5aff24fe38536f203 fa8df29bb9804ab5aff24fe38536f203] Unable to execute ['ovs-vsctl', '--timeout=120', '--oneline', '--format=json', '--db=tcp:127.0.0.1:6640', '--', '--if-exists', 'del-port', 'br-int', 'tapb205428b-83']. Exception: Unexpected error while running command. Open vSwitch `ovsdb-server` is not configured to listen on a TCP socket by default. Nova's default has recently changed [0]. Perhaps we should point Nova at the Unix socket Open vSwitch `ovsdb-server` listens to? Often instance creation succeeds, but I also see instance creation failures that correlate with the above messages. I have yet to establish any causation between the two events. 0: https://github.com/openstack/os-vif/blob/master/releasenotes/notes/add-ovsdb-native-322fffb49c91503d.yaml
2019-11-22 15:59:17 Alex Kavanagh charm-nova-compute: status New Triaged
2019-11-25 12:00:54 Frode Nordahl bug task added charm-ovn-chassis
2019-11-25 12:01:04 Frode Nordahl charm-ovn-chassis: status New Triaged
2019-11-25 12:01:10 Frode Nordahl charm-ovn-chassis: importance Undecided High
2019-11-25 12:01:14 Frode Nordahl charm-ovn-chassis: assignee Frode Nordahl (fnordahl)
2019-11-25 12:01:19 Frode Nordahl charm-ovn-chassis: status Triaged In Progress
2019-11-25 12:01:22 Frode Nordahl charm-nova-compute: status Triaged Invalid
2019-11-26 10:33:37 Frode Nordahl charm-ovn-chassis: status In Progress Fix Committed
2019-11-26 10:33:45 Frode Nordahl charm-ovn-chassis: milestone 20.01
2020-03-02 15:42:05 James Page charm-ovn-chassis: status Fix Committed Fix Released