network verification checker should test for ovs vlan issues
Bug #1350623 reported by
Andrew Woodward
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
High
|
Fuel Sustaining | ||
7.0.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
Mitaka |
Won't Fix
|
High
|
Registry Administrators |
Bug Description
There has been indications from the neutron mos team that newer kernels including Ubuntu nodes may still have issues with ovs vlans. To address this issue we should
add ovs code to bootstrapnode and run ovs-test to confirm if splinters are needed.
from (http://
It is not always easy to tell whether a Linux kernel driver has
buggy VLAN support. The ovs-vlan-test(8) and ovs-test(8) utilities
can help you test. See their manpages for details. Of the two
utilities, ovs-test(8) is newer and more thorough, but
ovs-vlan-test(8) may be easier to use.
Changed in fuel: | |
assignee: | nobody → Dima Shulyak (dshulyak) |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Dima Shulyak (dshulyak) → Fuel Python Team (fuel-python) |
milestone: | 6.0 → 6.1 |
tags: | added: feature |
tags: |
added: module-netcheck removed: nailgun |
tags: | added: qa-agree-7.0 |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
Changed in fuel: | |
status: | Triaged → Won't Fix |
tags: |
added: covered-by-bp removed: feature |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Triaged |
no longer affects: | fuel/8.0.x |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: wontfix-feature |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Networking (l23-network) |
Changed in fuel: | |
assignee: | Registry Administrators (registry) → l23network (l23network) |
Changed in fuel: | |
assignee: | Registry Administrators (registry) → nobody |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
To post a comment you must log in.
Currently we have limitations for our network verification architecture.
It is ok from the point of orchestration, but pretty ugly in terms of reporting and UI.
Some time ago i was proposing approach where we will have separate tab (or same as HealthCheck)
with all kinds of pre-deployment verifications enabled. It requires significant amount of work todo, and i am not sure
when i will have that free time.
If you want just prepare package and run it manually - it is very simple.. nailgun - it will require development and
But speaking of automation and integration it with our orchestrator/
testing, so i prefere to track this activity as BP.
https:/ /blueprints. launchpad. net/fuel/ +spec/ovs- test-part- network- verification