-
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
[1.5.0] Job scrolling upgrade compatibility failure #16307
Comments
Specify |
we are seeing a similar issue after upgrading our clients to 1.5.0 here is our job spec:
and the relevant client logs
as far as i can tell, the consul health checks are passing the entire time without issue (from consul's point of view). I'm not seeing anything in our consul logs regarding this alloc's health checks |
interesting - I updated by job spec to remove the deprecated "task network resources " and update those into the group network block, and now the job is working as expected. We knew that the old syntax was deprecated, but it was still working correctly up until this version. It might be nice to add a note in the upgrade guide regarding this Updated (working) job spec:
|
Hi @chenjpu and @gmichalec-pandora 👋 I have not being able to reproduce this yet. Would you be able to describe how your upgrade process was done? Did you update servers before clients? And which version of Consul are you running? |
Ah! I think this may be related to #16382. I didn't notice that you also have a dynamic service name @gmichalec-pandora do you happen to also have a dynamic service name? Or was the |
oh - yes! just tested by leaving the services/network config at the task level, but removing the |
to be clear, my service name was not dynamic, but the check name was:
|
Ah nice, thanks for the confirmation. I have a PR up to fix this problem 👍 |
Nomad version
1.5.0
Issue
1.Upgrade from 1.4.4 to 1.5.0![image](https://user-images.githubusercontent.com/1785778/222608356-f8fe80af-38f5-4574-ae8b-72b9945b01a4.png)
2.Release a new version of the job
3.
job
The text was updated successfully, but these errors were encountered: