Closed jasonmcintosh closed 7 years ago
What platform and version?
Sent from my iPhone JB
On Jan 31, 2017, at 17:50, Jason notifications@github.com wrote:
When testing, a reload of the service is occurring BEFORE consul has fully started (the delay happens almost immediately after the service start). This seems to cause consul to fail to start causing some tests to fail. I added a sleep block as a stop-gap:
ruby_block 'delay_reload_consul' do block do sleep 5 end end After a start of the service, but there's probably a better/cleaner way to handle this.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
CentOS 7, x86-64. COULD be a bug in consul, or in the service startup arguments. Just noticed it in here, thought I'd report it. I'll probably post a message to Consul as well.
It should be fixed by #427
Actually this particular behaviour will be fixed with #433 This should not be closed until #433 is merged
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
When testing, a reload of the service is occurring BEFORE consul has fully started (the delay happens almost immediately after the service start). This seems to cause consul to fail to start causing some tests to fail. I added a sleep block as a stop-gap:
After a start of the service, but there's probably a better/cleaner way to handle this.