+++ This bug was initially created as a clone of Bug #1272180 +++ Description of problem: When deploying keepalived controller Horizon won't load because the default vhost takes precedence over the horizon one. Version-Release number of selected component (if applicable): openstack-heat-templates-0.0.1-dev381.el7.centos.noarch openstack-tripleo-heat-templates-0.8.7-dev284.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy 1 x controller + 1 x compute with isolated networks and keepalived: openstack overcloud deploy --templates ~/templates/my-overcloud -e ~/templates/my-overcloud/environments/network-isolation.yaml -e ~/templates/network-environment.yaml -e ~/templates/firstboot-environment.yaml --control-scale 1 --compute-scale 1 --libvirt-type qemu 2. Check /etc/httpd/conf.d/ Actual results: Both 15-default.conf and 15-horizon_vhost.conf are present so the default takes precedence. Expected results: The horizon vhost takes precedence. Additional info: It looks that the non-pacemaker deployment doesn't set the vhost priority: https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/manifests/overcloud_controller.pp#L464
At this time, we don't support non-pacemaker deployments with director