Network problem definitely took place, however it seems that there were no retry attempts afterwards:
2017-01-03 03:47:50 ERROR [29198] Nodes ["2"] reached the response timeout
2017-01-03 03:47:50 WARNING [29198] Unable to get actual status of puppet on node 2. Reason: Nodes ["2"] reached the response timeout
2017-01-03 03:47:50 ERROR [29198] Node 2, task provision_2, manifest /etc/puppet/shell_manifests/provision_2_manifest.pp, status: undefined
2017-01-03 03:47:50 WARNING [29198] Error to get puppet status. Node 2, task provision_2, manifest /etc/puppet/shell_manifests/provision_2_manifest.pp.
2017-01-03 03:47:50 ERROR [29198] Node has failed to deploy. There is no more retries for puppet run. Node 2, task provision_2, manifest /etc/puppet/shell_manifests/provision_2_manifest.pp
and that is it, in case of more retries I would expect to see more messages like "Nodes ["2"] reached the response timeout"
Network problem definitely took place, however it seems that there were no retry attempts afterwards:
2017-01-03 03:47:50 ERROR [29198] Nodes ["2"] reached the response timeout shell_manifests /provision_ 2_manifest. pp, status: undefined shell_manifests /provision_ 2_manifest. pp. shell_manifests /provision_ 2_manifest. pp
2017-01-03 03:47:50 WARNING [29198] Unable to get actual status of puppet on node 2. Reason: Nodes ["2"] reached the response timeout
2017-01-03 03:47:50 ERROR [29198] Node 2, task provision_2, manifest /etc/puppet/
2017-01-03 03:47:50 WARNING [29198] Error to get puppet status. Node 2, task provision_2, manifest /etc/puppet/
2017-01-03 03:47:50 ERROR [29198] Node has failed to deploy. There is no more retries for puppet run. Node 2, task provision_2, manifest /etc/puppet/
and that is it, in case of more retries I would expect to see more messages like "Nodes ["2"] reached the response timeout"