Skip to content
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

Restart cavalcade on failure #81

Merged
merged 1 commit into from
Nov 22, 2019
Merged

Conversation

roborourke
Copy link
Contributor

Because the server is ready before WP is installed the runner starts and finds the table doesn't exist then promptly exits and stops the container. Not ideal!

@roborourke roborourke added backport v1-branch bug Existing functionality isn't behaving as expected labels Nov 22, 2019
Copy link
Member

@rmccue rmccue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a limit in this of some sort so it doesn't retry forever?

@roborourke
Copy link
Contributor Author

@rmccue that's not an available option, but presumably if there's some PHP error or whatever it should come back up. Guessing we do that on our infra?

@rmccue
Copy link
Member

rmccue commented Nov 22, 2019

On the infra, I believe it will retry ~5 times; it also retries again (5 times) when you deploy.

@roborourke roborourke merged commit 6baf421 into master Nov 22, 2019
@roborourke roborourke deleted the restart-cavalcade-on-fail branch November 22, 2019 16:04
@roborourke
Copy link
Contributor Author

I'll see what we can do in future but right now I can't find another way to ensure the service is available after the initial install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Existing functionality isn't behaving as expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants