Migration fails on user migration phase

Hi guys

I am trying to test migration path for an app, but I encountered a blocker. Migration fails on use migration phase with an error shown on in the screenshot. Migration fails instantly.

This issue occurs on fresh Jira Server and Jira Cloud instances. There’s one simple project and one admin user on the whole instance. Migration fails with " One or more users have an invalid email address" error message. However, all pre migration checks pass.

Furthermore, I was trying to use different domain in email - correct and dumblike ‘localhost.com’ or ‘domain.com’. None of those don’t work.

I think, the error message is incorrect, but I haven’t found any interesting things in Jira logs. Even if I enabled DEBUG level logs for com.atlassian.jira.migration classpath.

It may be important - migrations have been working properly last week. I assume my organization could made an under hood changes that might affect migration process. However, I am not able to identify source of problem.

Any ideas?

Environment:

  • Jira Server: tested on v8.20 and v8.0.0

  • Jira Cloud Migration Assistant: tested on v1.6.7 and v1.6.6

Cheers,

Kamil.

Hi @KamilKlimek,

Thanks for posting your question and sorry to hear you’ve had this issue. JCMA will check that each email address is unique and matches a basic email regex, but it’s not until we try and register them internally that the more precise checks occur, and domains like example.com and domain.com will generally fail.

To help us better, can you provide a recent migrationId from the server logs? That way we can see internally what’s going on.

Regards,
James.

I assumed that domains like example.com etc. may fail. That’s why I even tried to use gmail and my organization account emails. Unfortunately without success.

Here are few migrationIds

  • 6ba39d2f-a2be-472a-bf9f-354bbbe7dcad - with used my organization e-mail
  • 96959933-162c-4385-9eed-cd07f0d9774c - with used gmail account

If you need more details just let me know.

Cheers,
Kamil.

Hi @KamilKlimek,

We had a look at the logs and we can’t find anything conclusive. Can you run another test, create a Support Zip and open a DEVHELP ticket at Jira Service Management and attached the zip file?

Thanks,
James.

Hi guys

It’s been long time since I described the issue. Finally, I managed to resolve that with Atlassian support help.

As I assumed an error message was misleading and the issue doesn’t even relate to users’ email addresses. The problem was caused by missing SEN on Jira instance.

For development and testing purpose we use timebomb license and it turned out that one of them doesn’t generate SEN for an instance. However, “10 user Jira Software Data Center license, expires in 3 hours” license generates SEN and migrations go smoothly now. If you will ever encounter this issue, you can check your SEN here: /plugins/servlet/applications/versions-licenses - if it’s empty you should change license.

Here is official ecosystem ticket Jira Service Management

Cheers,
Kamil.

Hi,

Here’s a link to the public facing bug for this

Regards,
James.

1 Like