5d684eb59c
We should not run dns-client & ntp-client tasks for base-os role, because they setup vip_management address as dns/ntp server while we don't have setuped interfaces and hence that vip is unreachable. Moreover, we should not perform any "deployment" tasks on nodes of such type. It suppose to be "a node after provisioning" and that's it. In order to avoid this issue, let's specify explicitly on which roles we want to run dns-client & ntp-client tasks. Change-Id: Ie0375df4095de6d78ef167e9af1e18a962f48829 Closes-Bug: #1456661
21 lines
671 B
YAML
21 lines
671 B
YAML
- id: dns-server
|
|
type: puppet
|
|
groups: [primary-controller, controller]
|
|
required_for: [deploy_end]
|
|
requires: [openstack-haproxy]
|
|
parameters:
|
|
puppet_manifest: /etc/puppet/modules/osnailyfacter/modular/dns/dns-server.pp
|
|
puppet_modules: /etc/puppet/modules
|
|
timeout: 3600
|
|
|
|
- id: dns-client
|
|
type: puppet
|
|
role: [primary-mongo, mongo, primary-controller, controller, compute, ceph-osd, cinder, cinder-vmware, zabbix-server]
|
|
requires: [post_deployment_start]
|
|
required_for: [ntp-client]
|
|
parameters:
|
|
puppet_manifest: /etc/puppet/modules/osnailyfacter/modular/dns/dns-client.pp
|
|
puppet_modules: /etc/puppet/modules
|
|
timeout: 3600
|
|
cwd: /
|