No elastic agents assigned to pipelines

[Mohammad Umair]

Hello all,

I am new to GoCD. There is a problem with my gocd-server, i have created an elastic agent profile by mounting the volume with host volume, whenever i try to create more than one pipelines with the same elastic-agent profile no agents are provided to my pipelines rather than first pipeline

Please help me i dont understand this, why it is happening?

[Chad Wilson]

Is this with Kubernetes elastic agents or docker elastic agents?

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/975e7891-7532-40d8-ade9-08eda800208fn%40googlegroups.com.

[Mohammad Umair]

it is docker elastic agent.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAA1RwH9whaUZRNpd_WdYi9K_95K%2B-K4zxyu5oJqaoTLG6ZrPhQ%40mail.gmail.com.

[Chad Wilson]

OK. Can you share the snippet of your elastic agent configuration that specifies your host volume mount to show which folders you are mounting where in the container?

I am speaking in a generic way here since there isn't much detail shared about your use case, however generally host volumes can be problematic with such things if used for the writeable area (/godata), as each elastic agent really needs its own dedicated writeable space. If the second elastic agent isn't starting properly or isn't able to register with the server, you should be able to look at its container logs to see what the issue is.

I haven't tried it, but if you are bind mounting /godata to the same writeable host folder on each elastic agent, I suspect you will have problems - as each agent will have its own token issued by the server, which it needs to store locally, and might compete with each other to write to the space unless you only mount perhaps /godata/pipelines. If this is the issue the logs should indicate a server registration problem on one of the agents. if the 2nd container isn't starting at all, there should also be logs on the server side, or in the dedicated log for the elastic agent plugin in /godata/logs.

Can you share what you are trying to achieve with the host volume, i.e which data do you want to be persistent/shared between runs? Normally most elastic agent data is intended to be ephemeral and you want it to go away afterwards.

-Chad