Description of problem:
This seems like a regression from y1. This was not observed on y1. 

Version-Release number of selected component (if applicable):


How reproducible:
Deploy osp7y2 on RHEL 7.2, pass ntp address, only local address is configured. The ntp server is up and running post deployment but not with the appropriate server address.
Deployed overcloud with 
#!/bin/bash
openstack overcloud deploy --templates \
-e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/templates/network-environment.yaml \
-e /home/stack/templates/storage-environment.yaml \
-e /home/stack/templates/cisco-plugins.yaml \
-e /home/stack/templates/post_config.yaml \
--control-flavor control --compute-flavor compute --ceph-storage-flavor CephStorage \
--compute-scale 6 --control-scale 3  --ceph-storage-scale 3 \
--libvirt-type kvm \
--ntp-server 171.68.38.66 \
--neutron-network-type vlan \
--neutron-tunnel-type vlan \
--neutron-bridge-mappings datacentre:br-ex,physnet-tenant:br-tenant,floating:br-floating \
--neutron-network-vlan-ranges physnet-tenant:250:749,floating:160:160 \
--neutron-disable-tunneling --timeout 300 \
--rhel-reg --reg-method portal --reg-org org_id --reg-activation-key ACTIVATION_KEY \
--verbose --debug --log-file overcloud_new.log


Steps to Reproduce:
1.
2.
3.

Actual results:
The last 2 lines contain only 
server 127.127.1.0 # local clock address
fudge  127.127.1.0 stratum 10


Expected results:
Should have the server address --ntp-server 171.68.38.66  passed above.

Additional info: