Clone repo after newly provisioning Gitea consistently returns a 503

cloud-native-toolkit / terraform-tools-gitea

0 stars 1 forks source link

Clone repo after newly provisioning Gitea consistently returns a 503 #35

Closed seansund closed 1 year ago

seansund commented 1 year ago

It looks like the 503 error usually means migration is in progress/Gitea is still initializing everything - https://github.com/go-gitea/gitea/issues/1772. Not sure is this is per-repo or per-instance of Gitea. Currently this is only happening on OpenShift.

Assuming it is per-instance when Gitea is installed, we should add a wait until Gitea is ready.

Create a repo and try to clone it until it succeeds?

seansund commented 1 year ago

The issue appears to be a configuration problem with the Gitea instance. The http_url returned by the API is http instead of https.