Bug 968355
Summary: | Packstack has not loaded the 8021q module although vlan network type was chosen | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Rami Vaknin <rvaknin> |
Component: | openstack-packstack | Assignee: | Terry Wilson <twilson> |
Status: | CLOSED NOTABUG | QA Contact: | Nir Magnezi <nmagnezi> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.0 | CC: | aortega, derekh, rvaknin, twilson, yeylon, ykaul |
Target Milestone: | --- | ||
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-28 18:37:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rami Vaknin
2013-05-29 14:13:47 UTC
Has the lack of the kernel module being loaded actually caused an issue, or is this something that you expect to be needed yet haven't yet run into any specific bugs as a result of it not being loaded? To my knowledge, I haven't ever had to load this module when using quantum/openvswitch. Is it normally required? Or is that just for linuxbridge? I haven't run all our tests yet so I can't tell whether the lack of this module caused an issue, I just know that it was an installation step prior to OpenStack Networking support in packstack. In addition, I see that this module is not part of my kernel, it's only compiled as kernel module, are you sure that all the 8021q features work natively without the need to load this kernel module? # grep 8021Q /boot/config-`uname -r` CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y I'm pretty sure as I've never enabled it and have never seen anyone actually manually enabling it for using quantum/OVS. From what I can tell, the only reason you would need it when using OVS is if you were using brctl-compatibility. My recommendation would be to table this bug, until we actually find a problem that is being caused by this. I'm going to go ahead and close this as NOTABUG since it doesn't seem to cause any problems. If you run into an issue, feel free to re-open it. |