Fork not working gitlab-ce-8.14.3-ce.0.el7.x86_64

27 views
Skip to first unread message

Phil Evans

unread,
Dec 6, 2016, 7:48:53 PM12/6/16
to GitLab
Hi,

We recently upgraded gitlab-ce to version 8.14.2.
Since that upgrade we can no longer fork projects from the GUI.

Today, I did a yum update which installed a new version 8.14.3.
Unfortunately, the error is still happening.

I've attached a screenshot of the failed message from the fork.

As you'll see we're being told that the repository for this project does not exist.

When I look in /var/opt/gitlab/git-data/repositories/phile I can see that a directory called gowiki.wiki.git was created for my attempted fork, but not gowiki.git as I'd expect.

If I hit the remove project button from the screen attached, the gowiki.wiki.git directory is successfully removed.

There is plenty of disk space available on the server.

Server is running...
Red Hat Enterprise Linux Server release 7.3 (Maipo)


Thanks in advance,
Phil




Screenshot from 2016-12-07 13-39-31.png

T.J. Yang

unread,
Dec 7, 2016, 4:30:07 PM12/7/16
to GitLab
Hi Phil

I plan to do a 8.14.0 to 8.14.3 upgrade Friday.
I will add forking test as part of my post-upgrade test. 
If repo forked fail on 8.14.3 version then I will reverse back to 8.14.0.

Thanks for the warning

tj

Phil Evans

unread,
Dec 7, 2016, 4:46:07 PM12/7/16
to GitLab
Hi tj,

I raised a bug for this issue, too. https://gitlab.com/gitlab-org/gitlab-ce/issues/25390

And the response from the Gitlab team was excellent.

Turns out that somehow the JIRA Service Template was causing forking to fail!
So I just de-activated the Template and then forking magically started working again.
More info about the issue can be found here.... https://gitlab.com/gitlab-org/gitlab-ce/issues/25112

If you're not using that JIRA integration you should be fine.

If you are there are some new fields in the template you need to fill. 
Or you can just deactivate as I've done for now.


Kind regards,
Phil

T.J. Yang

unread,
Dec 9, 2016, 6:10:08 AM12/9/16
to GitLab
Hi Phil

Thanks for the info. I don't have fork issue since I was not using jira.
My 8.14.0 upgrade (to 8.14.4)  went fine this morning and  the forking test was ok.

tj
Reply all
Reply to author
Forward
0 new messages