kuryr-libnetwork

Bug #1854461
Comment #16

Comment 16 for bug 1854461

Revision history for this message

Edvinas Sulzickis (madness31) wrote on 2019-12-13: Re: [Bug 1854461] Re: BindingNotSupportedFailure: vif_type(binding_failed) is not supported

#16

And does this error from neutron-server says something for you? This error
is the only one I get from all logs

ERROR neutron.plugins.ml2.managers
[req-d5bb3e97-40b3-4261-aaea-dadad88537bf b3e7880917484f6899d79bdfa9f91cfc
0043ed77cd8b453d897d499c457d2247 - 3a3cd562d047408fbf743d22f2f22eb8
3a3cd562d047408fbf743d22f2f22eb8] Failed to bind port
2661688f-90b2-4c72-bd32-58acaf1c9a2c on host computei7-2 for vnic_type
normal using segments [{'id': '9f27f7c7-414c-4012-bed8-efe802ef1d31',
'network_type': 'gre', 'physical_network': None, 'segmentation_id': 43,
'network_id': 'cf5e6f43-2a0b-4015-8b8f-5fe8be335056'}]

On Sat, 30 Nov 2019 at 18:25, hongbin <email address hidden> wrote:

> It looks the port binding failed on neutron side, which is why vif_type
> is set to 'binding_failed'. Could you check neutron logs to see if there
> is any error message?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1854461
>
> Title:
> BindingNotSupportedFailure: vif_type(binding_failed) is not supported
>
> Status in kuryr-libnetwork:
> New
>
> Bug description:
> Hello, I used kuryr-libnetwork successfully for about a month, but
> unfortunately after full openstack reinstallation using juju I got
> error when trying to run docker container using kuryr-libnetwork
> directly on compute node. My juju bundle is the same like it used to
> be when it ran smoothly. Journalctl output is attached below
>
> docker version 19.03.2
>
> In /usr/local/libexec directory I have:
>
> bridge iovisor midonet ovs tap unbound
>
> * Installed Zun manually (source:
> https://docs.openstack.org/zun/stein/install/compute-install.html)
> * stable/stein version of Zun and Kuryr-libnetwork
> * Installed Kuryr-libnetwork manually (source:
> https://docs.openstack.org/kuryr-libnetwork/stein/install/compute-install-ubuntu.html
> )
> * OS Ubuntu 18.04.3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kuryr-libnetwork/+bug/1854461/+subscriptions
>

And does this error from neutron-server says something for you? This error
is the only one I get from all logs

On Sat, 30 Nov 2019 at 18:25, hongbin <hongbin034@gmail.com> wrote:

> It looks the port binding failed on neutron side, which is why vif_type
> is set to 'binding_failed'. Could you check neutron logs to see if there
> is any error message?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1854461
>
> Title:
>   BindingNotSupportedFailure: vif_type(binding_failed) is not supported
>
> Status in kuryr-libnetwork:
>   New
>
> Bug description:
>   Hello, I used kuryr-libnetwork successfully for about a month, but
>   unfortunately after full openstack reinstallation using juju I got
>   error when trying to run docker container using kuryr-libnetwork
>   directly on compute node. My juju bundle is the same like it used to
>   be when it ran smoothly. Journalctl output is attached below
>
>   docker version 19.03.2
>
>   In /usr/local/libexec directory I have:
>
>   bridge  iovisor  midonet  ovs  tap  unbound
>
>   * Installed Zun manually (source:
> https://docs.openstack.org/zun/stein/install/compute-install.html)
>   * stable/stein version of Zun and Kuryr-libnetwork
>   * Installed Kuryr-libnetwork manually (source:
> https://docs.openstack.org/kuryr-libnetwork/stein/install/compute-install-ubuntu.html
> )
>   * OS Ubuntu 18.04.3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kuryr-libnetwork/+bug/1854461/+subscriptions
>