After upgrading to 15.2.2 over the weekend CI jobs no longer created for our runners

GitLab CI/CD
1

Replace this template with your information

Describe your question in as much detail as possible: This weekend I upgraded our GitLab from 15.1.x to 15.2.2. After that, it seems like none of our repos will create jobs for our runners to deploy updates to the respective systems. We have made no changes to the configuration of these runners (other than making sure they are updated to the latest version available in apt) and if I manually go to Pipelines on a repo and “Run Pipeline”, it will pick up the changes and deploy them with the runner as it used to, just not automatically anymore.

  • What are you seeing, and how does that differ from what you expect to see?

hint: The ‘/var/opt/gitlab/gitaly/run/gitaly-32530/hooks-3994603796.d/pre-receive’ hook was ignored because it’s not set as executable.
hint: You can disable this warning with git config advice.ignoredHook false.
hint: The ‘/var/opt/gitlab/gitaly/run/gitaly-32530/hooks-3994603796.d/update’ hook was ignored because it’s not set as executable.
hint: You can disable this warning with git config advice.ignoredHook false.
hint: The ‘/var/opt/gitlab/gitaly/run/gitaly-32530/hooks-3994603796.d/reference-transaction’ hook was ignored because it’s not set as executable.
hint: You can disable this warning with git config advice.ignoredHook false.
hint: The ‘/var/opt/gitlab/gitaly/run/gitaly-32530/hooks-3994603796.d/post-receive’ hook was ignored because it’s not set as executable.
hint: You can disable this warning with git config advice.ignoredHook false.

Seeing these now when trying to do a “git push” after changes are made and committed. Was not seeing this prior to upgrade. Not sure if related but it is new as stated. I cannot just change the permissions on these to make it work as it is recreated every pipeline run as far as I can tell.

  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or GitLab.com?

    • GitLab (Hint: /help): 15.2.2
    • Runner (Hint: /admin/runners): 15.2.1

  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

stages:
- deploy

deploy:
stage: deploy
tags:
- hdpuppet
script:
- sudo /usr/local/bin/update_puppet_configs.sh

  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

I’ve tried restarting gitlab to make sure all services were running properly. I’ve tried restarting runners but it is ALL of our runners. I am not sure where I can look to see why jobs aren’t being created by runners.

2

I’ve also been notified our “Merge” interface is no longer loading per another employee.

Screen Shot 2022-08-16 at 12.25.39 PM
Screen Shot 2022-08-16 at 12.25.39 PM998×542 36 KB

3

What was the solution to your problem? I am having exactly the same issues.

4

Apparently it was a known issue with the 15.2 upgrade. They added info on how to fix it here:

5

Thanks Robert, it was indeed the noexec on my mount point as explained in the article.