-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polling tentacles need service restarted #55
Comments
I thought this might have been some interaction between octopus_deploy_tentacle 'Tentacle' do
action [:install, :configure]
version node['nd-octopus']['version']
checksum node['nd-octopus']['checksum']
trusted_cert node['nd-octopus']['trusted_cert']
end
octopus_deploy_tentacle 'Tentacle' do
action :register
server node['nd-octopus']['server']
api_key node['nd-octopus']['api_key']
roles node['nd-octopus']['roles']
environment node.chef_environment.to_s
polling node['nd-octopus']['polling']
configure_firewall node['nd-octopus']['configure_firewall']
end I've combined my 2 resources down to 1, but I'm still finding that the service restart is happening too early in the chef run.
|
Should the register resource restart the tentacle after it runs? |
Just saw #56 and merged it. Can you confirm if this fixes the issue or not? |
Trying to deploy octopus in mass. I find polling tentacles are installed properly, however they always fail their health check until I manually restart the service.
This is strange because the configure tentacle resource notifies the windows service to restart with a
:delayed
timer, yet it looks like the restart happens before the register action happens.The text was updated successfully, but these errors were encountered: