From a627681eec09eacd208b21d35ab7ad76245319e4 Mon Sep 17 00:00:00 2001
From: Ihar Hrachyshka <ihrachys@redhat.com>
Date: Fri, 29 Apr 2016 13:41:55 -0700
Subject: [PATCH] Stop configuring neutron to enforce DHCP MTU option

Since Mitaka, Neutron does the right job to calculate and advertise
correct MTU to instances, out of the box [1].

[1] https://review.openstack.org/#/c/302165/

TrivialFix
Change-Id: I71a6dc5b56c2c1fb9db757df77a56feababdc039
---
 ansible/roles/neutron/templates/dnsmasq.conf.j2 | 1 -
 1 file changed, 1 deletion(-)

diff --git a/ansible/roles/neutron/templates/dnsmasq.conf.j2 b/ansible/roles/neutron/templates/dnsmasq.conf.j2
index 70400db5ef..91566c4185 100644
--- a/ansible/roles/neutron/templates/dnsmasq.conf.j2
+++ b/ansible/roles/neutron/templates/dnsmasq.conf.j2
@@ -1,2 +1 @@
-dhcp-option-force=26,1450
 log-facility=/var/log/kolla/neutron/dnsmasq.log