kuryr bind port error with linux bridge driver

Bug #1638041 reported by Liping Mao
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Liping Mao

Bug Description

When use neutron linux bridge driver, container create failed on kuryr network.

Here is error log:
[2016-10-31 10:43:35,836] ERROR in controllers: Device "brfa:16:3e:df:" does not exist.
RTNETLINK answers: Invalid argument
/usr/local/libexec/kuryr/bridge: line 24: /sys/devices/virtual/net/brfa:16:3e:df:/bridge/forward_delay: No such file or directory
/usr/local/libexec/kuryr/bridge: line 25: /sys/devices/virtual/net/brfa:16:3e:df:/bridge/stp_state: No such file or directory
Cannot find device "brfa:16:3e:df:"
Error: argument "brfa:16:3e:df:" is wrong: Device does not exist

Liping Mao (limao)
Changed in kuryr:
assignee: nobody → Liping Mao (limao)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr (master)

Reviewed: https://review.openstack.org/391895
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=d241bbbb2fa15f46fcb54c744c986d67edd0afc4
Submitter: Jenkins
Branch: master

commit d241bbbb2fa15f46fcb54c744c986d67edd0afc4
Author: Liping Mao <email address hidden>
Date: Mon Oct 31 23:47:52 2016 +0800

    kuryr bind port error with neutron linux bridge driver

    When neutron configured with linux bridge driver, kuryr will bind
    port error. The linux bridge name should be "brq"+network_id[0,11].

    Change-Id: I07be68bbfe7b1384f4e946664aed41546ff9ddce
    Closes-bug: #1638041

Changed in kuryr:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kuryr 0.2.0

This issue was fixed in the openstack/kuryr 0.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers