https://www.puppet.com/community logo
Join Slack
Powered by
So... anyone ever have CD not able to update the p...
# continuous-delivery
r
So... anyone ever have CD not able to update the pipeline status on a gitlab merge request? We seem to have random modules not able to get their pipelines status after opening an MR and aren't really sure if its a CD issue or a Gitlab issue.
m
Do you see any errors in the CD logs when this happens? Fwiw I don’t think we’ve had a report of this from anyone. Is the issue recent, or has this always been a problem for you? I ask because we did make change to the way Gitlab pipelines get status updates in 5.15.0.
r
It's very recent… like right after 5.15.1
m
Does it only affect modules or also your control repo?
And to be clear, this is an issue of the status not showing up in Gitlab, on the PR? And when you say “random modules”, do those affected modules never get any updates? Or is it more like any given module might not get a certain status but the next time you run something in CD it does?
r
We haven't made a lot of changes to our control repos currently, but last week we ran in to the issue with one module . All the other modules that needed updated were working just fine. Finally somehow the one module with the issue started working... Thinking running 'gitlab-ctl reconfigure' helped, but we were totally sure. Today we had a different module start having the same issue. Tried the above command, tried rebooting, neither worked but then I closed our the MR and re-opened it and it was fine again.
yes, the status doesn't show up on the PR
One module was semi-frequently updated module and the one today probably less so
m
Okay, thanks. It might be worth you opening a support ticket if you keep seeing this. If you grab a support bundle right after you see it, the logs there might help us.
r
Will do
2 Views
Open in Slack
PreviousNext
Powered by