Bug 1254791
| Summary: | Bridge name "br-ex" hard coded in controller-puppet.yaml | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Dan Sneddon <dsneddon> |
| Component: | rhosp-director | Assignee: | Dan Sneddon <dsneddon> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | yeylon <yeylon> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | mburns, rhel-osp-director-maint, srevivo |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-03 14:29:59 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: | |||
This doesn't apply any more, we adjusted the templates to support {get_input: bridge_name} no matter what the value of bridge_name is.
|
Description of problem: In the compute templates, we assign the bridge_name parameter to the value of NeutronPhysicalBridge. This allows the --neutron-physical-bridge parameter on the command line to influence the bridge name in the NIC templates. Unfortunately, in the controller templates we hard-code the value to "br-ex", so if you use the --neutron-physical-bridge parameter your compute nodes will not have the same bridge name as your controller nodes, and VLAN mode networking won't work. Version-Release number of selected component (if applicable): 7 GA How reproducible: 100% Steps to Reproduce: 1. Use --neutron-physical-bridge command-line parameter 2. This sets NeutronPhysicalBridge, which sets bridge_name in compute tempates 3. Controller templates hard-code br-ex, so the command-line parameter fails to work. Actual results: Controllers *always* end up with br-ex as the name of the bridge where the VLANs terminate. Expected results: This should be influenced by a command-line parameter --neutron-physical-bridge Additional info: This was discovered while triaging a separate bug. While both of these bugs are in place, there is no way to make VLAN mode networking work (unless you replace the name of the bond "br-bond" in the compute.yaml with "br-ex" or "{get_input: bridge_name}". controller-puppet.yaml L585: bridge_name: br-ex