What do you do for the error Elasticsearch version not compatibleĬonfirm that your version of Elasticsearch or OpenSearch is compatible with your version of GitLab. That have been removed in the new version cannot be executed or retried. If you upgrade GitLab before all pending advanced search migrations are completed, any pending migrations To clean up the migration, upgrade to 15.1 or later.įor other advanced search migrations stuck in pending, see how to retry a halted migration. If you are a self-managed customer who uses GitLab 15.0 with advanced search, you will experience performance degradation. In GitLab 15.0, an advanced search migration named DeleteOrphanedCommit can be permanently stuck What do you do if your advanced search migrations are stuck? Sudo -u git -H bundle exec rake gitlab:elastic:list_pending_migrations Pause your runners, or block new jobs from starting by adding the following to your /etc/gitlab/gitlab.rb: To address the above two scenarios, it is advised to do the following prior to upgrading: However, depending on the error, the GitLab Runner either retries, or eventually terminates, job handling.Īs for the artifacts, the GitLab Runner attempts to upload them three times, after which the job eventually fails. When GitLab is back online, the trace updates should self-heal. If you upgrade your GitLab instance while the GitLab Runner is processing jobs, the trace updates fail. Dealing with running CI/CD pipelines and jobs Check for background migrations before upgradingĬertain releases may require different migrations to beįinished before you upgrade to the newer version.įor more information, see background migrations. See the guide to plan your GitLab upgrade.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |