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 | |
---|---|---|---|---|---|
kuryr |
Fix Released
|
Undecided
|
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/
/usr/local/
Cannot find device "brfa:16:3e:df:"
Error: argument "brfa:16:3e:df:" is wrong: Device does not exist
Changed in kuryr: | |
assignee: | nobody → Liping Mao (limao) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/391895 /git.openstack. org/cgit/ openstack/ kuryr/commit/ ?id=d241bbbb2fa 15f46fcb54c744c 986d67edd0afc4
Committed: https:/
Submitter: Jenkins
Branch: master
commit d241bbbb2fa15f4 6fcb54c744c986d 67edd0afc4
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 id[0,11] .
port error. The linux bridge name should be "brq"+network_
Change-Id: I07be68bbfe7b13 84f4e946664aed4 1546ff9ddce
Closes-bug: #1638041