Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo migration is not working in the new version 1.14.1 #15570

Closed
2 of 6 tasks
angelsanchez opened this issue Apr 21, 2021 · 2 comments
Closed
2 of 6 tasks

Repo migration is not working in the new version 1.14.1 #15570

angelsanchez opened this issue Apr 21, 2021 · 2 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/distribution This PR changes something about the packaging of Gitea type/bug

Comments

@angelsanchez
Copy link

angelsanchez commented Apr 21, 2021

  • Gitea version (or commit ref): 1.14.1
  • Git version: 2.30.2
  • Operating system: GNU/Linux Alpine 3.13.5
    We are using the official docker image in k8s:
image:
    repository: gitea/gitea
    tag: 1.14.1
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

The gitea container is logging this:

 2021/04/21 14:39:54 Started POST /api/v1/repos/migrate for 172.17.0.8:32768                                                                                                                           
 2021/04/21 14:39:54 Completed POST /api/v1/repos/migrate 409 Conflict in 37.199026ms

Description

  1. We are creating a new migration from a public github.com repository using the API /api/v1/repos/migrate

The API is returning the following error:

422 Unprocessable Entity

Migration failed: Clone: exit status 128 - fatal: unable to access 'https://github.com/go-gitea/gitea.git/': Could not resolve host: github.com

If we try to connect with github from the gitea instance, it fails:

# curl -vv https://github.com
* Could not resolve host: github.com
* Closing connection 0
curl: (6) Could not resolve host: github.com

The OS that is using the gitea docker image is:

# cat /etc/alpine-release 
3.13.5

Could be it related to gliderlabs/docker-alpine#539?

@angelsanchez angelsanchez changed the title Repo migration is not working in the new version 1.4.1 Repo migration is not working in the new version 1.14.1 Apr 21, 2021
@zeripath
Copy link
Contributor

Is this still a problem?

@zeripath zeripath added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label May 12, 2021
@angelsanchez
Copy link
Author

angelsanchez commented May 17, 2021

I have tested the new version 1.14.2 and the problem persists:

Could not resolve host: github.com

If I execute the following command inside the gitea instance, there is a DNS issue:

# ping github.com
ping: bad address 'github.com'

# nslookup -debug github.com
Server:		10.96.0.10
Address:	10.96.0.10:53
Query #0 completed in 2ms:
Name:	github.com
Address: 140.82.121.3
Query #1 completed in 2ms:
** server can't find github.com: NXDOMAIN

After researching and testing, it seems a problem with DNS resolution using the alpine:3.13 images on Minikube with the VirtualBox driver and it is related to: kubernetes/minikube#10830

@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
@delvh delvh added topic/distribution This PR changes something about the packaging of Gitea and removed theme/docker labels Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/distribution This PR changes something about the packaging of Gitea type/bug
Projects
None yet
Development

No branches or pull requests

4 participants