Do not set dhcp_domain in Nova from overcloud_domain_name

The dhcp_domain option was deprecated in Pike [1] and is causing
issues like [2] by configuring the shortname of nodes to their
fully qualified domain name.

1. https://github.com/openstack/nova/blob/stable/pike/nova/conf/network.py#L468
2. https://bugzilla.redhat.com/show_bug.cgi?id=1507888

Closes-Bug: 1733874
Change-Id: I4db66155b2c4ba8e0639ec00f938a8bc2ac85762
(cherry picked from commit e29de0a58c)
This commit is contained in:
Giulio Fidente 2017-11-15 18:07:15 +01:00
parent 1e0dd6786e
commit 0191cd4933
1 changed files with 0 additions and 1 deletions

View File

@ -409,7 +409,6 @@ nova::api_database_connection: mysql+pymysql://nova_api:{{UNDERCLOUD_NOVA_PASSWO
nova::placement_database_connection: mysql+pymysql://nova_placement:{{UNDERCLOUD_NOVA_PASSWORD}}@{{LOCAL_IP_WRAPPED}}/nova_placement
nova::notify_on_state_change: 'vm_and_task_state'
nova::scheduler::enabled: true
nova::network::neutron::dhcp_domain: {{OVERCLOUD_DOMAIN_NAME}}
nova::compute::force_config_drive: true
nova::compute::reserved_host_memory: '0'
nova::compute::vnc_enabled: false