Gitlab Migration - Revision history

Tallada: /* Issues and Troubleshooting */

2019-01-10T12:07:34Z

Issues and Troubleshooting

Jcasals: /* TCP connection reset by peer */

2019-01-09T09:33:33Z

TCP connection reset by peer

Jcasals at 09:33, 9 January 2019

2019-01-09T09:33:07Z

Tallada at 16:02, 13 December 2018

2018-12-13T16:02:42Z

Tallada at 15:59, 13 December 2018

2018-12-13T15:59:39Z

Tallada at 12:20, 13 December 2018

2018-12-13T12:20:45Z

Tallada at 11:57, 13 December 2018

2018-12-13T11:57:44Z

Tallada at 11:37, 26 October 2018

2018-10-26T11:37:43Z

Tallada at 11:37, 26 October 2018

2018-10-26T11:37:12Z

Tallada at 10:59, 26 October 2018

2018-10-26T10:59:19Z

← Older revision		Revision as of 12:07, 10 January 2019
Line 35:		Line 35:

	Please, update your Operating System or [https://confluence.atlassian.com/crucible/installing-and-upgrading-git-679608571.html try to update] your git version.		Please, update your Operating System or [https://confluence.atlassian.com/crucible/installing-and-upgrading-git-679608571.html try to update] your git version.
		+
		+	=== GitLab: The project you were looking for could not be found ===
		+
		+	Group members and permissions might have not been migrated. Please send a support request to astro@pic.es.

@@ Line 29: / Line 29: @@
 == Issues and Troubleshooting ==
 === TCP connection reset by peer ===
-You may be one of the few unlucky persons that see this error appearing when trying to clone or fetch from gitlab.
+You may be one of the few unlucky users that see this error appearing when trying to clone or fetch from gitlab.
   git clone https://gitlab.pic.es/user/repository.git
   fatal: unable to access 'https://gitlab.pic.es/user/repository.git': TCP connection reset by peer

← Older revision		Revision as of 09:33, 9 January 2019
Line 26:		Line 26:

	'''For users of projects (i.e. CTA) that already migrated, you still need to update your remote URL (step 3) to be able to take advantage of future upgrades.'''		'''For users of projects (i.e. CTA) that already migrated, you still need to update your remote URL (step 3) to be able to take advantage of future upgrades.'''
		+
		+	== Issues and Troubleshooting ==
		+	=== TCP connection reset by peer ===
		+	You may be one of the few unlucky persons that see this error appearing when trying to clone or fetch from gitlab.
		+	git clone https://gitlab.pic.es/user/repository.git
		+	fatal: unable to access 'https://gitlab.pic.es/user/repository.git': TCP connection reset by peer
		+	As [https://stackoverflow.com/questions/53594412/what-version-of-git-supports-tls-1-2#answer-53594630 this note] from Stack Overflow says, the version of the git package included on Red Hat version 5, lower than 6.8 and lower than 7.2 doesn't support TLSv1.2, the one needed for SSL transfers.
		+
		+	Please, update your Operating System or [https://confluence.atlassian.com/crucible/installing-and-upgrading-git-679608571.html try to update] your git version.

@@ Line 15: / Line 15: @@
      # Update the URL of the repository
      $ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)
      # Push everything to new remote

@@ Line 14: / Line 14: @@
      # Update the URL of the repository
-     $ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)
+     $ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)
      # Push everything to new remote

@@ Line 14: / Line 14: @@
      # Update the URL of the repository
-     $ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | sed s/gitlab01.pic.es/gitlab.pic.es/g)
+     $ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)
      # Push everything to new remote
@@ Line 20: / Line 20: @@
      $ git push origin --tags
-There will be a 3 month period where both gitlab host will coexist to give time users to migrate.
+'''For users of projects (i.e. CTA) that already migrated, you still need to update your remote URL (step 3) to be able to take advantage of future upgrades.'''

@@ Line 1: / Line 1: @@
-The gitlab service need to be upgraded to a new version and host.
+In order to upgrade the gitlab service, it was required to move it to a new host.
-It will be migrated from gitlab01.pic.es (running v6.x) to gitlab02.pic.es (running v11.x).
+The migration of the git repositories from the old host to the new one cannot be done transparently because the previous version has not easy upgrade procedure.
 For newer releases, all information will be preserved and the procedure will be done without any user intervention.
 '''Also, note that for this particular upgrade, all information from tickets, merge requests and wiki WILL NOT BE MIGRATED.'''
 In order to migrate your git repositories to the new host, follow these instructions:
-) If you use want to use SSH authentication, log into https://gitlab02.pic.es with your PIC credentials and upload your SSH keys.
+) Log into https://gitlab.pic.es with your PIC credentials
-) Execute the following commands on each directory that holds a repository that need migration:
+) If you use want to use SSH authentication, you have to upload the corresponding public key. You can access this from the ''Settings'' drop-down menu in the top-left of the screen.
-     # Create a remote called new_gitlab with the new address of the repository
+) For each git repository that you want to migrate, execute the the following commands onto the directory it resides:
-     $ git remote add new_gitlab $(git remote -v | awk '{print $2}' | sort -u | sed s/gitlab01.pic.es/gitlab02.pic.es/g)
-     # Upload the repository to the new remote
+     # Push everything to new remote
-     $ git push new_gitlab --all
+     $ git push origin --all
-     $ git push new_gitlab --tags
+     $ git push origin --tags
-−
 There will be a 3 month period where both gitlab host will coexist to give time users to migrate.

@@ Line 4: / Line 4: @@
 For newer releases this will be done without any user intervention.
-The upgrade of the service need to be done in two steps.
+In order to migrate your git repositories to the new host, follow these instructions:
-First, users must migrate their repositories to the new host following these instructions:
      # Create a remote called new_gitlab with the new address of the repository