forge/forge
13
10
Fork 9
Code Issues 99 Pull requests Projects Wiki Activity Actions

[RUNNER] New Forgejo Actions CI runner for FreeIPA organization #700

New issue
Closed
opened 2026-08-03 09:23:05 +00:00 by abbra · 6 comments
abbra commented 2026-08-03 09:23:05 +00:00
Copy link

Organization Name

freeipa

Use Case

We are migrating few projects from Codeberg where we used private runners (marked as 'vdali' in the workflows). I registered the same runner with the Fedora Forge and in general it works but sometimes it is denied from uploading results:

Aug 03 08:48:48 podman[23492]: time="2026-08-03T08:48:48Z" level=info msg="Received shutdown.Stop(), terminating!" PID=23492
Aug 03 08:48:50 systemd[1101]: podman.service: Consumed 1min 10.672s CPU time over 10min 12.208s wall clock time, 102.5M memory peak.
Aug 03 08:49:09 forgejo-runner[23481]: time="2026-08-03T08:49:09Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857
Aug 03 08:49:10 forgejo-runner[23481]: time="2026-08-03T08:49:10Z" level=warning msg="ReportLog error: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858
Aug 03 08:50:03 systemd[1101]: libpod-conmon-80d15ac4eb711beec8cd84f0b1f38da9e246c42d7d1a0b00c26faf76f2774c03.scope: Consumed 2.243s CPU time over 11min 21.442s wall clock time, 29.9M memory peak.
Aug 03 08:50:10 forgejo-runner[23481]: time="2026-08-03T08:50:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857
Aug 03 08:50:10 forgejo-runner[23481]: time="2026-08-03T08:50:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858
Aug 03 08:51:10 forgejo-runner[23481]: time="2026-08-03T08:51:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858
Aug 03 08:51:11 forgejo-runner[23481]: time="2026-08-03T08:51:11Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857
Aug 03 08:52:10 forgejo-runner[23481]: time="2026-08-03T08:52:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858
Aug 03 08:52:12 forgejo-runner[23481]: time="2026-08-03T08:52:12Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857
Aug 03 08:53:11 forgejo-runner[23481]: time="2026-08-03T08:53:11Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858
Aug 03 08:53:15 forgejo-runner[23481]: time="2026-08-03T08:53:15Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857
Aug 03 08:53:39 systemd[1101]: libpod-conmon-83e538dc37d1f07a7c70e56ef5791e0091ae9002e2061b86571ee8e7549dfa10.scope: Consumed 1.651s CPU time over 14min 57.615s wall clock time, 32.3M memory peak.

I saw similar issues with Codeberg as well but at much smaller scale.

I suspect we deal with the Fedora's infrastructure limits for non-trusted external resources (via Anubis?). It would be nice to have a runner that could work without these limitations.

The projects we need to test through the runners are primary written in Rust and thus are resource consuming, so probably enabling them for testing farm use is a better case.

Architecture Requirements

default (x86_64), aarch64

Runner type

testing-farm (minimal runner used only for running https://forge.fedoraproject.org/ci/testing-farm action)

Additional Context

No response

### Organization Name freeipa ### Use Case We are migrating few projects from Codeberg where we used private runners (marked as 'vdali' in the workflows). I registered the same runner with the Fedora Forge and in general it works but sometimes it is denied from uploading results: ``` Aug 03 08:48:48 podman[23492]: time="2026-08-03T08:48:48Z" level=info msg="Received shutdown.Stop(), terminating!" PID=23492 Aug 03 08:48:50 systemd[1101]: podman.service: Consumed 1min 10.672s CPU time over 10min 12.208s wall clock time, 102.5M memory peak. Aug 03 08:49:09 forgejo-runner[23481]: time="2026-08-03T08:49:09Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857 Aug 03 08:49:10 forgejo-runner[23481]: time="2026-08-03T08:49:10Z" level=warning msg="ReportLog error: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858 Aug 03 08:50:03 systemd[1101]: libpod-conmon-80d15ac4eb711beec8cd84f0b1f38da9e246c42d7d1a0b00c26faf76f2774c03.scope: Consumed 2.243s CPU time over 11min 21.442s wall clock time, 29.9M memory peak. Aug 03 08:50:10 forgejo-runner[23481]: time="2026-08-03T08:50:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857 Aug 03 08:50:10 forgejo-runner[23481]: time="2026-08-03T08:50:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858 Aug 03 08:51:10 forgejo-runner[23481]: time="2026-08-03T08:51:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858 Aug 03 08:51:11 forgejo-runner[23481]: time="2026-08-03T08:51:11Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857 Aug 03 08:52:10 forgejo-runner[23481]: time="2026-08-03T08:52:10Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858 Aug 03 08:52:12 forgejo-runner[23481]: time="2026-08-03T08:52:12Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857 Aug 03 08:53:11 forgejo-runner[23481]: time="2026-08-03T08:53:11Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6858 Aug 03 08:53:15 forgejo-runner[23481]: time="2026-08-03T08:53:15Z" level=warning msg="uploading final logs failed, but will be retried: deadline_exceeded: Post \"https://forge.fedoraproject.org/api/actions/runner.v1.RunnerService/UpdateLog\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" task_id=6857 Aug 03 08:53:39 systemd[1101]: libpod-conmon-83e538dc37d1f07a7c70e56ef5791e0091ae9002e2061b86571ee8e7549dfa10.scope: Consumed 1.651s CPU time over 14min 57.615s wall clock time, 32.3M memory peak. ``` I saw similar issues with Codeberg as well but at much smaller scale. I suspect we deal with the Fedora's infrastructure limits for non-trusted external resources (via Anubis?). It would be nice to have a runner that could work without these limitations. The projects we need to test through the runners are primary written in Rust and thus are resource consuming, so probably enabling them for testing farm use is a better case. ### Architecture Requirements default (x86_64), aarch64 ### Runner type testing-farm (minimal runner used only for running https://forge.fedoraproject.org/ci/testing-farm action) ### Additional Context _No response_
lenkaseg added this to the Sprint 26 project 2026-08-04 10:07:39 +00:00
lenkaseg commented 2026-08-05 13:52:41 +00:00
Member
Copy link

image

testing farm type runner scoped for 'freeipa' org is available, with label: 'testing-farm'

Use as:

    runs-on: testing-farm

Job concurrency: 20

You can see the config here: infra/ansible@195510e3b0/roles/openshift-apps/forgejo/runners/production/freeipa-1.yml

Let me know if everything works!

![image](/attachments/343f6629-ac53-4b99-80a6-689e8c31f2c7) testing farm type runner scoped for 'freeipa' org is available, with label: 'testing-farm' Use as: ``` runs-on: testing-farm ``` Job concurrency: 20 You can see the config here: infra/ansible@195510e3b0/roles/openshift-apps/forgejo/runners/production/freeipa-1.yml Let me know if everything works!
image.png
10 KiB
lenkaseg commented 2026-08-05 13:55:10 +00:00
Member
Copy link

Thats's for the x86_64 runner.

Do you want the arm64 as well? For simple job dispatch to testing farm the x86_64 should suffice, but no problem in adding one arm64 as well.

Thats's for the x86_64 runner. Do you want the arm64 as well? For simple job dispatch to testing farm the x86_64 should suffice, but no problem in adding one arm64 as well.
lenkaseg commented 2026-08-05 13:59:24 +00:00
Member
Copy link

I'll try to get more info about the anubis policy on selfhosted runners.

I'll try to get more info about the anubis policy on selfhosted runners.
abbra commented 2026-08-05 14:14:50 +00:00
Author
Copy link

@lenkaseg thank you. For job dispatches x86_64 is indeed enough, no need for arm64 then. I'll need to work on my side to make sure we request both types from the testing farm.

@lenkaseg thank you. For job dispatches x86_64 is indeed enough, no need for arm64 then. I'll need to work on my side to make sure we request both types from the testing farm.
abbra commented 2026-08-05 16:31:06 +00:00
Author
Copy link

Works fine: https://forge.fedoraproject.org/freeipa/ahdapa/actions/runs/12/jobs/0/attempt/2
and the testing farm result is here: https://artifacts.dev.testing-farm.io/387f9683-bed4-4849-8375-7e067e3aacc5/

Thank you!

Works fine: https://forge.fedoraproject.org/freeipa/ahdapa/actions/runs/12/jobs/0/attempt/2 and the testing farm result is here: https://artifacts.dev.testing-farm.io/387f9683-bed4-4849-8375-7e067e3aacc5/ Thank you!
abbra closed this issue 2026-08-05 16:31:06 +00:00
lenkaseg commented 2026-08-07 11:07:20 +00:00
Member
Copy link

Glad it works!
If there's any problem, let me know!

Glad it works! If there's any problem, let me know!
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
test
docs
Clear current reference
No results found.
Labels
Clear labels   
ai-review-please
label for requesting AI code review

  
Org/Team Modification

   
Private Issues
Label for tracking development on Private Issues in Forgejo

  
Runner Request
  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
ai-review-please
Org/Team Modification
Private Issues
Runner Request
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 26
Assignees
Clear assignees
No assignees
lenkaseg
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forge/forge#700
No description provided.