-
Notifications
You must be signed in to change notification settings - Fork 2k
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
please upgrade vendored consul #6785
Comments
This commit is responsible for FTBFS against Consul 1.5.3: hashicorp/consul@f09af53 |
FYI @tgross. Due to this issue I can not upgrade Consul v1.5.2 in Debian... Thanks. |
A first fallout of this problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950736 Consul is affected by CVE-2020-7219 and CVE-2020-7955 but I can not upgrade Consul in Debian because it will break Nomad. :(( How can I convince you to care more about interoperability, integration and consistency between your own software components? CC: @tgross. |
As previously discussed, we'll be doing this vendor upgrade in the 0.11 timeframe. |
Thanks. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
At the moment Nomad only builds against Consul 1.4.*.
Nomad FTBFS with Consul 1.5+ because
github.com/hashicorp/consul/lib/freeport
has been moved github.com/hashicorp/consul/sdk/freeport
.Furthermore Consul 1.5.3 introduced breaking change to
github.com/hashicorp/consul/agent/consul/autopilot
that causes the following FTBFS:Please consider upgrading vendored Consul.
Thanks.
The text was updated successfully, but these errors were encountered: