-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[feature]: cli job run retry on "Error fetching deployment" #12062
Comments
Hey @resmo This would be a great feature to have so thanks for making this, we'll address this internally and get back to you with our thoughts 👍. Would you be willing to raise a PR for this? |
Thanks @Amier3 I am afraid, I don't have much experience in golang. |
Hi all! @DerekStrickland do you have any news about that? |
@DerekStrickland @tgross Hi! Any news? |
@bubejur we'll update issues when we're working on them. This isn't currently on our immediate roadmap. |
This would be helpful for us too! Thanks for suggesting this change. |
We upgraded our CI pipeline to use nomad cli 1.5.5 (from 1.4.4). So ... this feature would be much appreciated. |
Doubling down on @vkrebs-wktaa comment. I just upgraded from 1.3.x to 1.5.6 and now I see this error almost every time I |
Hi all 👋 Just noting here that, while investigating #17320, I noticed that the deployment monitor was not outputting the actual error that happened, which makes it hard to understand what problem is happening, so I've opened #17348 to improve this. A retry mechanism would indeed be helpful, so I'm keeping this one opened. |
Any news about this? |
As this software no longer has an osi approved license, closing... |
Proposal
Add an option --retry (default 3) for monitoring the job run status.
Use-cases
We run a reverse proxy as a cetralized entry point for our devs to the nomad API. The proxy itself runs on nomad.
If our CI re-deploys that proxy accessing the API through that proxy, even with canary and rolling update it might be the cli errors out with "Error fetching deployment".
We added a retry on error in our CI, but we wished the CLI job monitoring would just retry a couple of times by itself e.g. 3 times with a delay of a second.
Attempted Solutions
canary and rolling update
The text was updated successfully, but these errors were encountered: