Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
8.20.16, 9.4.6
-
None
-
8.2
-
Severity 3 - Minor
-
Description
Issue Summary
Rows in the nodeassocation that refer to a project ID that does not exist in the project table appear in the nodeassociation table.
According to the KB:
https://confluence.atlassian.com/jirakb/500-cacheexception-error-thrown-during-upgrade-restore-of-jira-server-800858895.html
this has been observed to happen after project deletion.
Steps to Reproduce
The issue is not reproducible.
Actual Results
Rows in the nodeassocation that refer to a project ID that does not exist in the project table appear in the nodeassociation table.
Expected Results
All the rows in nodeassociation that refer to a project refer to an exisiting project.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- relates to
-
JRASERVER-70651 Invalid rows in nodeassocation will cause a cluster-wide outage
- Closed