Add openvswitch-common to neutron-api/consolidated rocks

[MylesJP]

The neutron-api package now runs under apache+mod_wsgi instead of as a standalone neutron-server process. When mod_wsgi imports the WSGI application, neutron.server.api publishes a PROCESS/BEFORE_SPAWN event on every worker fork, which triggers OVNMechanismDriver.pre_fork_initialize. That callback shells out to ovsdb-client which was missing previously.

[hemanthnakkina]

The neutron-api package now runs under apache+mod_wsgi instead of as a standalone neutron-server process. When mod_wsgi imports the WSGI application, neutron.server.api publishes a PROCESS/BEFORE_SPAWN event on every worker fork, which triggers OVNMechanismDriver.pre_fork_initialize. That callback shells out to ovsdb-client which was missing previously.

neutron uses python libraries ovs and ovsdbapp to communicate with ovs/ovn https://opendev.org/openstack/neutron/src/branch/master/requirements.txt#L46

What exactly the issue you are facing? We may not require openvswitch-common

[MylesJP]

The neutron-api package now runs under apache+mod_wsgi instead of as a standalone neutron-server process. When mod_wsgi imports the WSGI application, neutron.server.api publishes a PROCESS/BEFORE_SPAWN event on every worker fork, which triggers OVNMechanismDriver.pre_fork_initialize. That callback shells out to ovsdb-client which was missing previously.

neutron uses python libraries ovs and ovsdbapp to communicate with ovs/ovn https://opendev.org/openstack/neutron/src/branch/master/requirements.txt#L46

What exactly the issue you are facing? We may not require openvswitch-common

I'm getting this error in the neutron pebble logs:

neutron_lib.callbacks.exceptions.CallbackFailure: Callback
neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize
failed with "[Errno 2] No such file or directory: 'ovsdb-client'"

The traceback comes from the pre_fork_initialize method which calls this method. It looks like that was added 4 years ago but maybe it just wasn't exercised? I think it may only be used under mod_wsgi.

[hemanthnakkina]

The neutron-api package now runs under apache+mod_wsgi instead of as a standalone neutron-server process. When mod_wsgi imports the WSGI application, neutron.server.api publishes a PROCESS/BEFORE_SPAWN event on every worker fork, which triggers OVNMechanismDriver.pre_fork_initialize. That callback shells out to ovsdb-client which was missing previously.

neutron uses python libraries ovs and ovsdbapp to communicate with ovs/ovn https://opendev.org/openstack/neutron/src/branch/master/requirements.txt#L46
What exactly the issue you are facing? We may not require openvswitch-common

I'm getting this error in the neutron pebble logs:

neutron_lib.callbacks.exceptions.CallbackFailure: Callback
neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize
failed with "[Errno 2] No such file or directory: 'ovsdb-client'"

The traceback comes from the pre_fork_initialize method which calls this method. It looks like that was added 4 years ago but maybe it just wasn't exercised? I think it may only be used under mod_wsgi.

Ok I see it now. Prior to Resolute, we use neutron-server which is a meta package that contains openvswitch-common as well. As part of the split, only neutron-api package is installed instead of neutron-server and so other necessary packages like openvswitch-common should be installed as part of rock.

[hemanthnakkina]

@MylesJP Can you push the signed commit