ovs-agent doesn't configure new ovs-port for an instance
Bug #1512358 reported by
Mikhail Chernik
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Invalid
|
High
|
MOS Neutron | ||
| 7.0.x |
Invalid
|
High
|
MOS Neutron | ||
Bug Description
On MOS-7.0 (build 301) with DVR on 200-nodes lab environment several rally scenarios (e.g. boot_and_
ovs-agent still cannot create port, but proceeds further.
fuel version: http://
Rally traceback for boot_and_
Node: http://
nova-all log on node-704: http://
ovs in nova-all.log: http://
ovs-agent log: http://
| Changed in mos: | |
| milestone: | none → 7.0-mu-2 |
| assignee: | nobody → MOS Neutron (mos-neutron) |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in mos: | |
| milestone: | 7.0-mu-2 → 7.0-updates |
| Changed in mos: | |
| milestone: | 7.0-updates → 8.0 |
| status: | Confirmed → New |
| Changed in mos: | |
| status: | New → Invalid |
Revision history for this message
| Denis Meltsaykin (dmeltsaykin) wrote | #1 |
To post a comment you must log in.
Closing as Invalid, as the corresponding change seems to be merged and there is no progress tracked in this bug report.