Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-54570

Import from another Cloud Confluence instance throws GroupNotFoundException

      Summary

      Importing from another Cloud Confluence instance throws the error GroupNotFoundException

      Environment

      Confluence Cloud

      Steps to Reproduce

      1. Create two Cloud Confluence instances with same version.
      2. Create backup from Instance #1 from backup manager
      3. Import to Instance #2. Import will fail and roll back with:

        Import failed. Check your server logs for more information. com.atlassian.crowd.exception.runtime.GroupNotFoundException: Group does not exist

      Expected Results

      The import from one Confluence instance to the other should have been successful

      Actual Results

      The instance throws the error GroupNotFoundException

      @4000000053b6c805014ad174 2014-07-05 01:27:55,019 ERROR [Long running task: Importing data] [confluence.importexport.actions.ImportLongRunningTask] runInternal Failure during import
      @4000000053b6c805014ad55c  -- url: /wiki/admin/import/doimportconfluencesite.action | userName: sysadmin | referer: https://subcon.atlassian.net/wiki/admin/import/importconfluencesite.action | action: doimportconfluencesite
      @4000000053b6c805014ad944 com.atlassian.confluence.user.UserManagementOperationFailedException: com.atlassian.crowd.exception.runtime.GroupNotFoundException: Group <atlassian-addons> does not exist
      @4000000053b6c805014af0b4       at com.atlassian.confluence.user.DefaultUserAccessor.addMembership(DefaultUserAccessor.java:173)
      @4000000053b6c805014af0b4       at bucket.user.DefaultUserAccessor.addMembership(DefaultUserAccessor.java:488)
      
      com.atlassian.crowd.exception.runtime.GroupNotFoundException: Group <_licensed-confluence> does not exist
      

      Solution / Workaround

      1. Add a new group in the target instance (dummy-group is the name I chose)
      2. Edit the XML backup to replace _licensed-confluence with dummy-group
      3. Re-import

            [CONFCLOUD-54570] Import from another Cloud Confluence instance throws GroupNotFoundException

            The workaround is not working.

            Felix Loranger added a comment - The workaround is not working.

            Thank you

            kumporn kaewkor added a comment - Thank you

            This issue is not resolved, and while it also causes the import to fail, it is not related to CONF-36040.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - This issue is not resolved, and while it also causes the import to fail, it is not related to CONF-36040 .

            Issues related to site import are now being tracked under https://jira.atlassian.com/browse/CONF-36040. Closing this ticket as duplicate. Please watch/vote for https://jira.atlassian.com/browse/CONF-36040 if you are still interested in this issue.

            Brendan McNamara (Inactive) added a comment - Issues related to site import are now being tracked under https://jira.atlassian.com/browse/CONF-36040 . Closing this ticket as duplicate. Please watch/vote for https://jira.atlassian.com/browse/CONF-36040 if you are still interested in this issue.

            As a workaround you can create a dummy-group before the import on the target Cloud instance, extract the backup's zip and open the 'entities.xml' file.
            Do a search for 'group-name' (the name of the group that's not being found) and replace all occurrences with the dummy-group name you previously created and save the file.
            Zip all the files again (maintaining the original structure) and re-try the import.

            Felipevsw (Inactive) added a comment - As a workaround you can create a dummy-group before the import on the target Cloud instance, extract the backup's zip and open the 'entities.xml' file. Do a search for 'group-name' (the name of the group that's not being found) and replace all occurrences with the dummy-group name you previously created and save the file. Zip all the files again (maintaining the original structure) and re-try the import.

            We're still having this issue..

            Patrick van der Rijst added a comment - We're still having this issue..

              fxu Feng Xu (Inactive)
              smackie@atlassian.com Shannon S
              Affected customers:
              13 This affects my team
              Watchers:
              32 Start watching this issue

                Created:
                Updated:
                Resolved: