gitlab 10.6.4-0051 upgrade

The discussion lounge for third-party packages.
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
algodata
I'm New!
I'm New!
Posts: 2
Joined: Fri Jul 13, 2018 6:36 am

gitlab 10.6.4-0051 upgrade

Unread post by algodata » Fri Jul 13, 2018 10:53 am

The last upgrade mention that the data will be migrate from MariaDB to PGsql automatically.

But it doesn't so we do not have accès to our repository anymore.

Is there a way to migrated data by our own ?

loure
I'm New!
I'm New!
Posts: 1
Joined: Fri Jul 13, 2018 12:41 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by loure » Fri Jul 13, 2018 12:44 pm

I have the same problem. Need help to migrate data between databases

snakedoctor13
Rookie
Rookie
Posts: 34
Joined: Mon Oct 04, 2010 4:19 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by snakedoctor13 » Fri Jul 13, 2018 8:28 pm

Same here. I should have wait..
It sounds like the db migration did not work.

spiTcz
I'm New!
I'm New!
Posts: 2
Joined: Sun Aug 31, 2014 5:25 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by spiTcz » Sat Jul 14, 2018 7:45 am

same problem ...

snakedoctor13
Rookie
Rookie
Posts: 34
Joined: Mon Oct 04, 2010 4:19 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by snakedoctor13 » Sun Jul 15, 2018 10:11 pm

I tried to migrate the data accordingly to the Gitlab documentation but I faced weird problems
https://gitlab.com/gitlab-org/gitlab-ce ... tgresql.md
I had to delete some columns because the pgloader was raising an error saying that the column didn't exist in postgres schema.
I managed to make pgloader work and I could see my repositories in Gitlab but Gitlab has some weird behaviours now. My guess is that''s because of the data I lost during migration. I can't even push on my repos..

I also tried the method given here since the Gitlab package is based on sameersbn docker image but without any success either. (the psql converted file is full of errors)
https://github.com/sameersbn/docker-gitlab/issues/429

Our best chance is to ask Gitlab (they are providing the synology package) what going on and what can we do to migrate our data manually. I'm going to ask for some help on their forum.
That's really not cool to be stuck like this !

snakedoctor13
Rookie
Rookie
Posts: 34
Joined: Mon Oct 04, 2010 4:19 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by snakedoctor13 » Sun Jul 15, 2018 10:32 pm

I posted in the Gitlab forum.
https://forum.gitlab.com/t/synology-git ... iled/17501

Let's see if anyone can help us there as well.

algodata
I'm New!
I'm New!
Posts: 2
Joined: Fri Jul 13, 2018 6:36 am

Re: gitlab 10.6.4-0051 upgrade

Unread post by algodata » Mon Jul 16, 2018 11:19 am

I've open a ticket to the synology support center.

They try to access to our NAS to fix it...

to be continue...

snakedoctor13
Rookie
Rookie
Posts: 34
Joined: Mon Oct 04, 2010 4:19 pm

Re: gitlab 10.6.4-0051 upgrade

Unread post by snakedoctor13 » Mon Jul 16, 2018 9:52 pm

What kind of ticket did you opened?
I couldn't find Gitlab under Packages on the support page (both from package center support page in DSM and there https://account.synology.com/fr-fr/supp ... ate/ticket).
Hope they'll find a fix or a procedure..

Post Reply

Return to “Third-party Packages”