Projects::ImportService::Error: Failed to replace snippets because one or more of the new records could not be saved. Award emoji...

https://sentry.gitlab.net/gitlab/gitlabcom/issues/719933/

Projects::ImportService::Error: Failed to replace snippets because one or more of the new records could not be saved. Award emoji is invalid
  lib/gitlab/import_export/importer.rb:24:in `execute'
    raise Projects::ImportService::Error.new(@shared.errors.join(', '))
  app/services/projects/import_service.rb:111:in `import_data'
    unless importer.execute
  lib/gitlab/metrics/instrumentation.rb:163:in `import_data'
    super
  app/services/projects/import_service.rb:24:in `execute'
    import_data
  lib/gitlab/metrics/instrumentation.rb:163:in `execute'
    super
...
(8 additional frame(s) were not displayed)

Projects::ImportService::Error: Failed to replace snippets because one or more of the new records could not be saved. Award emoji is invalid
  lib/gitlab/import_export/importer.rb:27:in `rescue in execute'
    raise Projects::ImportService::Error.new(e.message)
  lib/gitlab/import_export/importer.rb:21:in `execute'
    if import_file && check_version! && restorers.all?(&:restore) && overwrite_project
  app/services/projects/import_service.rb:111:in `import_data'
    unless importer.execute
  lib/gitlab/metrics/instrumentation.rb:163:in `import_data'
    super
  app/services/projects/import_service.rb:24:in `execute'
    import_data
...
(9 additional frame(s) were not displayed)

Projects::ImportService::Error: Failed to replace snippets because one or more of the new records could not be saved. Award emoji is invalid

added typebug label

GitLab.com, GitLab Enterprise Edition 11.11.0-ee

I created a very simple snippet and gave it a thumbsup. When trying to import (as admin), it threw this error.

Latest attempt that threw an error: Kibana link: https://log.gitlab.net/app/kibana#/doc/AWNABDRwNDuQHTm2tH6l/pubsub-sidekiq-inf-gprd-2019.05.23/doc?id=AWrmhgr_FxYu2nSczUFg&_g=h@44136fa

From export, relevant part of project.json from sample project (internal):

"snippets": [
        {
            "author_id": 2454149,
            "award_emoji": [
                {
                    "awardable_type": "Snippet",
                    "created_at": "2019-05-23T00:19:50.637Z",
                    "id": 1778048,
                    "name": "thumbsup",
                    "updated_at": "2019-05-23T00:19:50.637Z",
                    "user_id": 2454149
                }
            ],
            "content": "for import testing",
            "created_at": "2019-05-23T00:19:47.486Z",
            "description": "for import testing",
            "file_name": "",
            "id": 1859597,
            "notes": [],
            "project_id": 7618626,
            "title": "test snippet",
            "updated_at": "2019-05-23T00:19:47.486Z",
            "visibility_level": 0
        }

added Manage [DEPRECATED] devopsmanage severity3 labels

previous attempt that threw this error: https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6752#note_173422294

for this customer, we agreed to remove the (one) instance of award_emoji in order for the import to succeed.

Note at time of export, customer's version was GitLab version 11.10.4 CE

added DEPRECATED_project import label

bronze customer affected by this: https://gitlab.zendesk.com/agent/tickets/122239

added customer label

added reproduced on GitLab.com label

Thanks very much for the help. If there is any data needed from the instance I'm exporting from I'd be happy to provide it.

@edd.trent can you let us know which version of GitLab you have? That might help

marked this issue as related to #61934 (closed)

mentioned in issue #62341 (closed)

The version when the export ran was 11.10.4 but this project is old and was created when the instance was running 10.6.x.

added groupoptimize label

mentioned in issue #62644 (closed)

mentioned in issue #61934 (closed)

Setting ~"group::measure" based on ~"project import".

mentioned in issue #65331 (closed)

added 1 deleted label and removed groupoptimize label

added [deprecated] Accepting merge requests label

removed [deprecated] Accepting merge requests label

mentioned in issue #66126 (moved)

mentioned in issue #66221 (closed)

mentioned in issue #66563 (closed)

mentioned in issue #66854 (moved)

mentioned in issue #67156 (closed)

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue