Unable to use 'cni' driver with Linux bridge network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zun |
Fix Released
|
Critical
|
hongbin |
Bug Description
On a system which isn't running OVS, Zun appears to have a missing piece when configured to use the 'cni' driver for containers or the 'cri' driver for capsules.
I receive the following traceback when attempting to start a container:
Dec 01 08:48:51 aio1 zun-compute[11226]: Traceback (most recent call last):
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: mgr = _VIF_MANAGERS[
Dec 01 08:48:51 aio1 zun-compute[11226]: KeyError: 'bridge'
Dec 01 08:48:51 aio1 zun-compute[11226]: During handling of the above exception, another exception occurred:
Dec 01 08:48:51 aio1 zun-compute[11226]: Traceback (most recent call last):
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: timer()
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: cb(*args, **kw)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: func(*args, **kwargs)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: return f(*args, **kwargs)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: pci_requests, limits)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: return function(self, context, *args, **kwargs)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: limits)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: unset_host=True)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: self.force_
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: six.reraise(
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: raise value
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: requested_volumes)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: security_
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: subnets)
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: name=vif_
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: warn_on_
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: self._init_
Dec 01 08:48:51 aio1 zun-compute[11226]: File "/openstack/
Dec 01 08:48:51 aio1 zun-compute[11226]: (self.namespace, name))
Dec 01 08:48:51 aio1 zun-compute[11226]: stevedore.
As far as I can see from https:/
Is there a way around this which I am missing, or has this not been implemented? At present my workaround is to use 'kuryr' for containers and 'docker' for capsules.
CNI linux bridge driver is not implemented yet. Will do it as soon as possible.