Reviewed: https://review.opendev.org/c/openstack/nova/+/848948 Committed: https://opendev.org/openstack/nova/commit/cbf9b2b8739453e07fd3ca9724559a6eaa4332f6 Submitter: "Zuul (22348)" Branch: master
commit cbf9b2b8739453e07fd3ca9724559a6eaa4332f6 Author: Sean Mooney <[email protected]> Date: Thu Jul 7 12:46:32 2022 +0100 update nova-next and nova-ovs-hybrid-plug to disable linuxbridge neutron now declares linuxbridge experimental and requires it to be enabled by a new config option. We do not set that in these jobs so the neutron server fails to load since we enable the linux bridge mech driver. we do not actully use linuxbridge in these jobs so this patch just disables the mech driver. Change-Id: I129a850c3327498d26d899c7709f5749622afdd8 Closes-Bug: #1980948 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1980948 Title: adapt ci to neutron making linux bridge experimental Status in OpenStack Compute (nova): Fix Released Status in os-vif: Fix Released Bug description: tl;dr neutron now considers linuxbridge which uses to be the default mech driver in docs to be experimental and it is now guarded by a config flag. we do not set it in our jobs that have the mech driver loaded but not used so neutron fails to start. recently i noticed that gate jobs were failing with + functions-common:test_with_retry:2384 : timeout 60 sh -c 'while ! wget --no-proxy -q -O- http://10.209.98.53:19696; do sleep 0.5; done' + functions-common:test_with_retry:2385 : die 2385 'Neutron did not start' dining into this a little more we see Jul 06 16:21:46.635396 ubuntu-focal-rax-ord-0030301377 neutron- server[90491]: INFO neutron.plugins.ml2.managers [-] Configured mechanism driver names: ['openvswitch', 'linuxbridge'] Jul 06 16:21:46.640517 ubuntu-focal-rax-ord-0030301377 neutron- server[90491]: ERROR neutron.common.experimental [-] Feature 'linuxbridge' is experimental and has to be explicitly enabled in 'cfg.CONF.experimental' the nova-ovs-hybrid-plug and nova-next jobs both enable the linuxbridge mech driver but don't actually use it since they only deploy ovs. https://github.com/openstack/nova/blob/512fbdfa9933f2e9b48bcded537ffb394979b24b/.zuul.yaml#L138= https://github.com/openstack/nova/blob/512fbdfa9933f2e9b48bcded537ffb394979b24b/.zuul.yaml#L394= 7 days ago https://github.com/openstack/neutron/commit/7f0413c84c4515cd2fae31d823613c4d7ea43110 merged moving linux bridge to experimental so all jobs that have it enabled either need to remove it form the mech drivers list or enable it in the config via the new option. for nova-next and nova-ovs-hybrid-plug we can just remove the driver form the list for os-vif the os-vif-linuxbridge need to enable it via the new config option To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1980948/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
