Error in AdminArea after upgrading to 17.3.1

Problem to solve

After upgrading Gitlab from v17.2.4 to v17.3.1
i tried to change some options in UI Admin Area > Settings > General > Visibility and access controls and got error:

In logs found this:

NoMethodError (undefined method 'max_artifacts_content_include_size' for #<ApplicationSettings>....
Did you mean?  max_artifacts_size)

Steps to reproduce

  • Install self-managed Gitlab v17.3.1
  • Go to Admin Area > Settings > General > Visibility and access controls and change any setting
  • Click Save Changes

Configuration

image

Versions

  • Self-managed

Versions

  • GitLab v17.3.1
1 Like

Try going to Admin โ†’ Settings โ†’ CI/CD โ†’ Continuous Integration and Deployment and check the entries that relate to artifacts size and maximum includes and then save here to see if that helps.

Failing that you will need to check and make sure all database migrations have finished, or whether some have failed during previous upgrades. See here: Background migrations and upgrades | GitLab and here: Troubleshooting | GitLab to use the commands to ensure migration has finished. This link will also help check the status of migrations: Maintenance Rake tasks | GitLab

3 Likes

Issue seems to be resolved after re-saving changes on Admin โ†’ Settings โ†’ CI/CD โ†’ Continuous Integration and Deployment.
Thanks a lot

2 Likes

Crosslinking Undefined error with dynamic pipeline creation following upgrade of self hosted Gitlab to 17.3.1 (#481986) ยท Issues ยท GitLab.org / GitLab ยท GitLab as it seems to be the same problem or at least have the same root cause. We internally also had another case where restarting all the pods/nodes resolved the issue.