Opened 10 months ago
Closed 9 months ago
#3148 closed task (fixed)
Woodie thinks there are over 100K agents
Reported by: | strk | Owned by: | robe |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2024-I |
Component: | SysAdmin/Woodie | Keywords: | |
Cc: |
Description
According to https://woodie.osgeo.org/admin/settings#agents there is an indefinite number of agents, with scrolling down exposing more and more.
When visiting https://woodie.osgeo.org/admin/settings#queue I see agents numbered with identifiers such as 116330 which seems hardly the reality.
I've asked in the Woodpecker CI Matrix room and was asked if we are using WOODPECKER_AGENT_CONFIG_FILE but I cannot answer that by only looking at ansible-deployment (which does have a role but not much within it)
Change History (3)
comment:1 by , 10 months ago
comment:2 by , 10 months ago
Hmm okay this could be because we don't have a folder config token file set up for the agents. I do see the error once in a while about it not being able to find it's config file.
comment:3 by , 9 months ago
Milestone: | Unplanned → Sysadmin Contract 2024-I |
---|---|
Resolution: | → fixed |
Status: | new → closed |
okay I purged all the agents using the CI and reregistered the agents we have this time making sure they have a /etc/woodpecker folder and that an agent.conf is created when they launched.
I think the issue might have been the file didn't exist and couldn't be created cause the folder path did not exist, so they kept on getting new ids.
I also in the agents screen, set the name, cause it was given hash ids for names for each of the agents for some reason - https://woodie.osgeo.org/admin#agents
I still can't see the name exposed on the runs, but at least on the queue page when an agent is running https://woodie.osgeo.org/admin#queue you'll see the repo it's running and it's number, which you can easily reconcile to the server, cause I added the number to the name on the agents tab.
Sounds like known upstream: https://github.com/woodpecker-ci/woodpecker/issues/2027
Possibly helpful: https://woodpecker-ci.org/docs/administration/agent-config#agent-registration