Bug 1246589
| Summary: | we specify 3 dhcp_agents_per_network when there is only 1 controller | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marios Andreou <mandreou> |
| Component: | python-tripleoclient | Assignee: | Marios Andreou <mandreou> |
| Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | achernet, dmacpher, hbrock, jslagle, mandreou, mburns, rhel-osp-director-maint |
| Target Milestone: | --- | Keywords: | Triaged, ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tripleoclient-0.0.11-5.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
In older deployments using the python-rdomanager-oscplugin (not the python-tripleoclient) for Overcloud deployment, the dhcp_agents_per_network parameter for neutron was set to a minimum of 3, even in the case of a non-HA single controller deployment. This meant the dhcp_agents_per_network was set to 3 when deploying with only 1 Controller. This fix takes into account the single Controller case. The director sets at most 3 dhcp_agents_per_network and never more than the number of Controllers. Now if you deploy in HA with 3 or more controller nodes, the dhcp_agents_per_network configuration parameter in neutron.conf on those Controller nodes will be set to '3'. Alternatively if you deploy in non-HA with only 1 Controller, this same dhcp_agents_per_network parameter will be set to '1'.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-07 21:38:25 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
Marios Andreou
2015-07-24 15:51:47 UTC
Is this still an issue? or did we end up fixing it? (In reply to Mike Burns from comment #3) > Is this still an issue? or did we end up fixing it? no we are still setting to three afaics in the rdomanager plugin code so the fix for this was at https://review.gerrithub.io/#/c/241104 - this is a downstream only fix since it is in the rdomanager plugin. That was abandoned because the fix was included in https://review.gerrithub.io/#/c/241111/. In the end neither of these landed. I tried reviving the /#/c/241104 but failed (marked as closed and i am not gfidente), so I opened a new review at https://review.gerrithub.io/#/c/246108 rebased against master and also pointing here. thanks. upstream review @ https://review.openstack.org/#/c/221398/ and bug report at https://bugs.launchpad.net/tripleo/+bug/1493445 python-tripleoclient-0.1.1-4.el7ost.noarch [root@overcloud-controller-0 heat-admin]# grep -rni 'dhcp_agents_per' /etc/neutron/* /etc/neutron/neutron.conf:262:# dhcp_agents_per_network = 1 /etc/neutron/neutron.conf:263:dhcp_agents_per_network = 1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0604.html |