"An error occurred while merging. Try again." - but merged ?!

This started happening out of the blue after some of the recent upgrades. GITLAB-CI on CENTOS

a developer creates a merge request, I approve merge request, merge request is simple without any reason to fail, I click on “MERGE” button and I get

I check the master and all the changes are merged to master ?!?!? I can’t find “what failed”

We are not using CI/CD, no “.gitlab-ci.yml”, no pipelines, no jobs, no schedules…

I have no idea why merges are failing nor now to get actual log data on what is failing. anyone can help?

Same problem here, found nothing in the logs.
Also unable to find anything in the GitLab CE repo.

Got this error yesterday. Can’t find why my merge work but still show this.
My teams is double checking if everything work, but still.

well glad to know I’m not the only one, started happening recently … code gets merged into target branch but merge fails and I can’t find anything in any logs why it failed :frowning:

this is starting to be a serious issue not a single merge is passing?!

this is spreading, was only one repo now is few… anyone figured out what’s going on?

Anyone can suggest where to find a log of the “error occurred…”

@dude4004 did you maybe figure something out, I’m having this #%^^^@# spread, every merge request failed … I can’t find what failed in any of the logs

nah, we kept getting this error every day. It beginned since we upgraded our version and only happen with 1 environnement. All our other doesn’t have this error.

I opened a ticket on their website but they didn’t responded because I am not hosting at gitlab.com but on my server.

Only option left is to contact their support but I think it’s not free.

it is spreading here, it was happening on one repo only and now it spread to 2 more :frowning:
I’ll setup a new VM install it from scratch and load backup, maybe it will work, maybe not, we’ll see … if not I’ll try to mirror repos to new server, maybe that will work … I’m more afraid if this happened more other stuff can happen too… especially as I can’t find anywhere what the actual error is :frowning: no logs show the error

Just to confirm issue happen to someone else.