error: gitea auth token "laconic-so-publication-token" already exists but no CERC_GITEA_AUTH_TOKEN was provided #295

New Issue

zramsay · 2023-04-06T22:19:13Z

zramsay commented

2023-04-06 22:19:13 +00:00

keywords: "already exists" ... but where? Apparently I didn't nuke everything when starting over

both CERC_NPM_AUTH_TOKEN and CERC_GITEA_AUTH_TOKEN are unset

$ laconic-so --stack package-registry deploy up  
[+] Running 4/4
 ⠿ Network laconic-39cfbfefd0c2ac05f266c6d58c5dcc87_gitea       Created                                                                                           0.0s
 ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-db-1      Started                                                                                           0.4s
 ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-runner-1  Started                                                                                           0.5s
 ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-server-1  Started                                                                                           0.7s
{
  "key": 0,
  "value": {
    "id": 1,
    "name": "laconic-so-publication-token",
    "sha1": "",
    "token_last_eight": "abfccb9e",
    "scopes": [
      "sudo"
    ]
  }
}
FATAL error: gitea auth token "laconic-so-publication-token" already exists but no CERC_GITEA_AUTH_TOKEN was provided
FATAL Error running command: /Users/mito/cerc/hosting/gitea/initialize-gitea.sh

keywords: "already exists" ... but where? Apparently I didn't nuke everything when starting over both `CERC_NPM_AUTH_TOKEN` and `CERC_GITEA_AUTH_TOKEN` are unset ``` $ laconic-so --stack package-registry deploy up [+] Running 4/4 ⠿ Network laconic-39cfbfefd0c2ac05f266c6d58c5dcc87_gitea Created 0.0s ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-db-1 Started 0.4s ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-runner-1 Started 0.5s ⠿ Container laconic-39cfbfefd0c2ac05f266c6d58c5dcc87-server-1 Started 0.7s { "key": 0, "value": { "id": 1, "name": "laconic-so-publication-token", "sha1": "", "token_last_eight": "abfccb9e", "scopes": [ "sudo" ] } } FATAL error: gitea auth token "laconic-so-publication-token" already exists but no CERC_GITEA_AUTH_TOKEN was provided FATAL Error running command: /Users/mito/cerc/hosting/gitea/initialize-gitea.sh ```

dboreham commented

2023-04-06 22:35:03 +00:00

This happens if you re-deploy gitea without blowing away its data (how to do that is currently undocumented).
I think it might be benign in that the old token should still be valid.
The confusing error message is trying to say that if you had defined CERC_GITEA_AUTH_TOKEN with the value of the old token, then the script would run without error.

This happens if you re-deploy gitea without blowing away its data (how to do that is currently undocumented). I think it might be benign in that the old token should still be valid. The confusing error message is trying to say that if you had defined `CERC_GITEA_AUTH_TOKEN` with the value of the old token, then the script would run without error.

zramsay commented

2023-04-06 22:39:06 +00:00

ah, so much hunch was correct ... but where is the gitea data, because I blew everything away with docker system prune -a before starting

ah, so much hunch was correct ... but where is the gitea data, because I blew everything away with `docker system prune -a` before starting

dboreham commented

2023-05-30 12:38:40 +00:00

ah, so much hunch was correct ... but where is the gitea data, because I blew everything away with docker system prune -a before starting

rm -rf ~/cerc/hosting/gitea/gitea
rm -rf ~/cerc/hosting/gitea/postgres
rm -rf ~/cerc/hosting/gitea/act-runner

> ah, so much hunch was correct ... but where is the gitea data, because I blew everything away with `docker system prune -a` before starting ``` rm -rf ~/cerc/hosting/gitea/gitea rm -rf ~/cerc/hosting/gitea/postgres rm -rf ~/cerc/hosting/gitea/act-runner ```

zramsay commented

2023-09-27 21:47:32 +00:00

i have a much better handle on all this now

Sign in to join this conversation.

No Milestone

No project

No Assignees

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: cerc-io/stack-orchestrator#295