#3148: Woodie thinks there are over 100K agents
-----------------------------+-----------------------
Reporter: strk | Owner: robe
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Woodie | Keywords:
-----------------------------+-----------------------
According to Woodpecker there is an
indefinite number of agents, with scrolling down exposing more and more.
When visiting Woodpecker 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)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3148>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3148: Woodie thinks there are over 100K agents
-----------------------------+------------------------
Reporter: strk | Owner: robe
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Woodie | Resolution:
Keywords: |
-----------------------------+------------------------
Comment (by strk):
Sounds like known upstream: https://github.com/woodpecker-
ci/woodpecker/issues/2027
Possibly helpful: https://woodpecker-ci.org/docs/administration/agent-
config#agent-registration
--
Ticket URL: <#3148 (Woodie thinks there are over 100K agents) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3148: Woodie thinks there are over 100K agents
-----------------------------+------------------------
Reporter: strk | Owner: robe
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Woodie | Resolution:
Keywords: |
-----------------------------+------------------------
Comment (by robe):
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.
--
Ticket URL: <#3148 (Woodie thinks there are over 100K agents) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3148: Woodie thinks there are over 100K agents
-----------------------------+---------------------------------------
Reporter: strk | Owner: robe
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin/Woodie | Resolution: fixed
Keywords: |
-----------------------------+---------------------------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
* milestone: Unplanned => Sysadmin Contract 2024-I
Comment:
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 -
Woodpecker
I still can't see the name exposed on the runs, but at least on the queue
page when an agent is running Woodpecker 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.
--
Ticket URL: <#3148 (Woodie thinks there are over 100K agents) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.