You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the number of server replicas is increased, the new servers don't get ACL tokens applied to them and so they can't function properly.
The way the initial set of servers get their ACL tokens is via the server-acl-init Job that makes an agent token update API call. This is then stored on persistent disk for each of those servers. When a new server comes up as a result of increasing the number of replicas, it doesn't have an ACL token on disk and the server-acl-init job doesn't make the token update API call because it thinks the servers are already bootstrapped.
A workaround for now is to manually retrieve the agent-token from Consul and manually apply it to the new servers.
The text was updated successfully, but these errors were encountered:
* Add acceptance tests for health checks on consul-ent
* update ci timeouts because of ns delete taking a while
* add helper function to make tests pass
If the number of server replicas is increased, the new servers don't get ACL tokens applied to them and so they can't function properly.
The way the initial set of servers get their ACL tokens is via the
server-acl-init
Job that makes an agent token update API call. This is then stored on persistent disk for each of those servers. When a new server comes up as a result of increasing the number of replicas, it doesn't have an ACL token on disk and the server-acl-init job doesn't make the token update API call because it thinks the servers are already bootstrapped.A workaround for now is to manually retrieve the
agent-token
from Consul and manually apply it to the new servers.The text was updated successfully, but these errors were encountered: