Closed cpressland closed 1 month ago
Hi @cpressland
Sorry that this isn't working for you. It looks like the agent is failing to communicate with server using our RPC protocol.
Am I correct in assuming you are self-hosting Octopus Server?
If so, is the port 10943
open on the Octopus Server machine and accessible from the cluster?
Hi @APErebus - we got to the bottom of this after a week or so of hacking and trying different things.
agent.serverCommsAddress
to point to an Azure Load Balancer, we swapped to using agent.serverCommsAddresses
and hitting each server directly.serverCommsAddress
to serverCommsAddresses
the agent went from intermittent to completely non-functional. This turned out to be that the agent only configures trusts for remote servers on its first launch, if you change this list after deployment it'll silently ignore those "new" servers and just sit there doing nothing, forever. We solved this by uninstalling the agent and reinstalling each time we had to make a config change.I think I should raise another issue to get logging improved for this failure condition, else, I'll go ahead and close this off.
Team
What happened?
When creating a Kubernetes Octopus Tentacle via either Helm or Flux the agent initially connects and registers itself as a deployment target, After this initial registration the agent refuses to perform any tasks. For example, when running a Health Check the task sits on
Determining ScriptService version to use
for six minutes before timing out.Reproduction
Installation of the Kubernetes Agent helm chart at either 1.16.1 or 2.2.1. In the below example I'm using Flux but the same thing happens when using the steps provided by the Octopus Deploy Web UI.
Error and Stacktrace
Pod Logs:
More Information
^^ This never finishes even when doing this from the UI.
Workaround
No response