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
Because this service is "magical" it is not in the agent's registered list, and targeting a remote exec does not work. We need to handle being a server-mode agent to respect this service.
The text was updated successfully, but these errors were encountered:
@armon I've been exploring this a bit today. I noticed that consul itself is what is registering the "consul" service. I've been able to also get the service registered in the agent with a few simple lines. I think we can probably take the registration out of consul itself now and let the anti-entropy handle it. The question now is how we get any guarantee that the anti-entropy has run. Right now, l.changeMade() is just called from the AddService() method on localState, so if that runs immediately after starting the server (likely before any leader is elected), I'm not sure it will work reliably. This definitely creates problems for the tests as well.
* add ci config to pull s3 dev builds for tests
* pick some initial oss/ent hashes of dev builds
* use env var properly
* use the directory flag properly to untar
* use sudo for tar to access /usr/local/bin
duckhan
pushed a commit
to duckhan/consul
that referenced
this issue
Oct 24, 2021
Because this service is "magical" it is not in the agent's registered list, and targeting a remote exec does not work. We need to handle being a server-mode agent to respect this service.
The text was updated successfully, but these errors were encountered: