[brencher] Create reverseproxy mirrors on gitea (admin + hermes) — blocks deploy #25

Open
opened 2026-08-30 21:48:28 +02:00 by hermes · 0 comments
Contributor

Create reverseproxy mirrors on gitea (blocks brencher deploy)

Context

After PR #23 (feat(configs): point torrserv_proxy at gitea admin/hermes repos) was deployed (brencher rebuilt at auto-98ee950a-e081fea4), the new multi-remote config for torrserv_proxy.py started failing in a tight retry loop:

ERROR - Failed to fetch updates for https://gitea.rudolf.keenetic.link/admin/reverseproxy
fatal: Authentication failed for 'https://gitea.rudolf.keenetic.link/admin/reverseproxy/'

Root cause: admin/reverseproxy and hermes/reverseproxy do not exist on gitea.rudolf.keenetic.link. Only admin/brencher and admin/ansible exist there:

$ GET /api/v1/users/admin/repos
  admin/brencher
  admin/ansible

admin/reverseproxy → 404
hermes/reverseproxy → 404

So brencher's git fetch on the gitea_admin remote fails → clone aborted → retry loop → torrserv_proxy deploy never completes.

What needs to happen

Create the two missing gitea mirrors and seed them from github.com/rudolf1/reverseproxy:

Gitea repo Source
gitea.rudolf.keenetic.link/admin/reverseproxy github.com/rudolf1/reverseproxy
gitea.rudolf.keenetic.link/hermes/reverseproxy github.com/rudolf1/reverseproxy

Mirroring can be one-shot git push --mirror from the github clone, or a periodic sync job (existing act_runner / cron can handle that).

Why this matters

Blocks all four multi-remote migrations under #18 (the parent migration ticket), not just #23. Without reverseproxy mirrors, any config that wants remotes=[...] for torrserv_proxy-like stacks (using a non-brencher, non-ansible repo) will fail at clone time with the same Authentication failed error.

The single-remote form (url="...") still works for reverseproxy because brencher has fallback creds for github on the legacy path — but that's exactly what #18 is trying to retire.

Acceptance criteria

  • gitea.rudolf.keenetic.link/admin/reverseproxy exists and has at least the same branches as github.com/rudolf1/reverseproxy (including main).
  • gitea.rudolf.keenetic.link/hermes/reverseproxy exists with the same.
  • brencher's torrserv_proxy clone loop stops failing: next cycle log shows git fetch gitea_admin returning 0, not fatal: Authentication failed.
  • torrserv_proxy stack gets redeployed with expected_version == actual_version after brencher picks up the new config (matches PR #23).

Verification

# 1. Repo exists
curl -sS -o /dev/null -w "%{http_code}\n" \
  -H "Authorization: token $GITEA_TOKEN" \
  'https://gitea.rudolf.keenetic.link/api/v1/repos/admin/reverseproxy'
# expect: 200

curl -sS -o /dev/null -w "%{http_code}\n" \
  -H "Authorization: token $GITEA_TOKEN" \
  'https://gitea.rudolf.keenetic.link/api/v1/repos/hermes/reverseproxy'
# expect: 200

# 2. brencher no longer in fail-loop
docker logs <brencher-container-id> --tail 100 | grep "Authentication failed for 'https://gitea.rudolf.keenetic.link/admin/reverseproxy"
# expect: (no output)

# 3. stack deploys with new version
docker service ls --filter name=torrserv_proxy
# expect: image updated, expected_version == actual_version

Note on PR #8 pattern

PR #8 (feat(configs): point hermes_infra at gitea admin/hermes ansible repos) only used gitea-remote'ы and avoided github entirely. That works because admin/ansible already existed on gitea. For reverseproxy we have no such foundation yet — this ticket creates it.

Refs #23
Blocks #18 (parent migration ticket)

## Create `reverseproxy` mirrors on gitea (blocks brencher deploy) ### Context After PR #23 ([feat(configs): point torrserv_proxy at gitea admin/hermes repos](https://gitea.rudolf.keenetic.link/admin/brencher/pulls/23)) was deployed (brencher rebuilt at `auto-98ee950a-e081fea4`), the new multi-remote config for `torrserv_proxy.py` started failing in a tight retry loop: ``` ERROR - Failed to fetch updates for https://gitea.rudolf.keenetic.link/admin/reverseproxy fatal: Authentication failed for 'https://gitea.rudolf.keenetic.link/admin/reverseproxy/' ``` Root cause: `admin/reverseproxy` and `hermes/reverseproxy` **do not exist** on `gitea.rudolf.keenetic.link`. Only `admin/brencher` and `admin/ansible` exist there: ``` $ GET /api/v1/users/admin/repos admin/brencher admin/ansible ``` `admin/reverseproxy` → 404 `hermes/reverseproxy` → 404 So brencher's git fetch on the `gitea_admin` remote fails → clone aborted → retry loop → `torrserv_proxy` deploy never completes. ### What needs to happen Create the two missing gitea mirrors and seed them from `github.com/rudolf1/reverseproxy`: | Gitea repo | Source | |---|---| | `gitea.rudolf.keenetic.link/admin/reverseproxy` | `github.com/rudolf1/reverseproxy` | | `gitea.rudolf.keenetic.link/hermes/reverseproxy` | `github.com/rudolf1/reverseproxy` | Mirroring can be one-shot `git push --mirror` from the github clone, or a periodic sync job (existing `act_runner` / cron can handle that). ### Why this matters Blocks all four multi-remote migrations under #18 (the parent migration ticket), not just #23. Without `reverseproxy` mirrors, any config that wants `remotes=[...]` for `torrserv_proxy`-like stacks (using a non-brencher, non-ansible repo) will fail at clone time with the same `Authentication failed` error. The single-remote form (`url="..."`) still works for `reverseproxy` because brencher has fallback creds for github on the legacy path — but that's exactly what #18 is trying to retire. ### Acceptance criteria - `gitea.rudolf.keenetic.link/admin/reverseproxy` exists and has at least the same branches as `github.com/rudolf1/reverseproxy` (including `main`). - `gitea.rudolf.keenetic.link/hermes/reverseproxy` exists with the same. - brencher's `torrserv_proxy` clone loop stops failing: next cycle log shows `git fetch gitea_admin` returning 0, not `fatal: Authentication failed`. - `torrserv_proxy` stack gets redeployed with `expected_version == actual_version` after brencher picks up the new config (matches PR #23). ### Verification ```bash # 1. Repo exists curl -sS -o /dev/null -w "%{http_code}\n" \ -H "Authorization: token $GITEA_TOKEN" \ 'https://gitea.rudolf.keenetic.link/api/v1/repos/admin/reverseproxy' # expect: 200 curl -sS -o /dev/null -w "%{http_code}\n" \ -H "Authorization: token $GITEA_TOKEN" \ 'https://gitea.rudolf.keenetic.link/api/v1/repos/hermes/reverseproxy' # expect: 200 # 2. brencher no longer in fail-loop docker logs <brencher-container-id> --tail 100 | grep "Authentication failed for 'https://gitea.rudolf.keenetic.link/admin/reverseproxy" # expect: (no output) # 3. stack deploys with new version docker service ls --filter name=torrserv_proxy # expect: image updated, expected_version == actual_version ``` ### Note on PR #8 pattern PR #8 (`feat(configs): point hermes_infra at gitea admin/hermes ansible repos`) only used gitea-remote'ы and avoided github entirely. That works because `admin/ansible` already existed on gitea. For `reverseproxy` we have no such foundation yet — this ticket creates it. Refs #23 Blocks #18 (parent migration ticket)
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/brencher#25