helpernode playbook run fails when running it subsequently

[yussufsh]

While changing the trigger for running helpernode on change of worker count the playbook fails. As we are masking the named and haproxy service manually in automation the helpernode fails to use it.

Error:

module.install.null_resource.config (remote-exec):^[[0m ^[[0mTASK [Starting services] *******************************************************
module.install.null_resource.config (remote-exec):^[[0m ^[[0m^[[0;31mfailed: [192.168.25.32] (item=named) => {"ansible_loop_var": "item", "changed": false, "item": "named", "msg": "Unable to enable service named: Failed to enable unit: Unit file /etc/systemd/system/named.service is masked.\n"}^[[0m
module.install.null_resource.config (remote-exec):^[[0m ^[[0m^[[0;31mfailed: [192.168.25.32] (item=haproxy) => {"ansible_loop_var": "item", "changed": false, "item": "haproxy", "msg": "Unable to enable service haproxy: Failed to enable unit: Unit file /etc/systemd/system/haproxy.service is masked.\n"}^[[0m

Resolution: Use helpernode dhcp.dns to set to something other than bastion IP. In this case haproxy and named won't be running on bastion.