Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.4.2, 6.4.4, 6.4.11, 7.0.4, 7.0.9, 7.1.1, 7.2.0, 7.1.8, 7.2.2, 7.5.0
-
6.04
-
48
-
Severity 3 - Minor
-
1
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
When migrating from Cloud to Server, the directory poller job is not removed for the previous Crowd User Directory (aka Horde).
Steps to Reproduce
- Export from a JIRA Cloud instance.
- Import it into JIRA Server.
Expected Results
There are no noticeable errors.
Actual Results
The following exception is thrown:
2015-05-04 10:45:36,829 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR [com.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory com.atlassian.crowd.exception.DirectoryNotFoundException: Directory <10000> does not exist at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:71) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) at org.quartz.core.JobRunShell.run(JobRunShell.java:223) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Additionally viewing the Scheduler Administration page will present errors as per the attached screenshot.
Workaround
You can remove the orphaned job directly from the database as per our Directory Sync Throws Error "Directory <2> does not exist" KB article.
Notes
When this is fixed, please include an upgrade task to clean up existing records, or some provide some SQL as a workaround that can be used to fix the problem.
Attachments
Issue Links
- relates to
-
-
- Closed
-