Issue Summary

During zero downtime upgrade, when one of the nodes is using Jira 8.17.0, the project permission changes will not be propagated.

Steps to Reproduce

1. Set up a cluster with two nodes, one of them using 8.17.0, the other with 8.16.x or 8.17.1
2. Open issue security level permissions in a browser on both nodes to ensure they are cached.
3. Change issue security level permissions for a user.

Expected Results

After refresh, both nodes should show the same, updated permissions.

Actual Results

Only the node that originated the change will show the updated permissions.

Workaround

Nodes on 8.17.0 will communicate that change between themselves, but not to other versions. They will also not accept changes from other versions.

Workaround #1: If the permission was updated on the 8.17.0 node, it needs to be repeated on non-8.17.0 nodes (and vice versa).
Workaround #2: If you updated the permission on 8.17.0 node, all non-8.17.0 need to be restarted (this can be a rolling restart). Likewise, if you performed a change on a non-8.17.0 node, 8.17.0 nodes will need to be restarted.

Actions to be taken after ZDU upgrade that involved a 8.17.0 version:

After the last node running 8.17.0 is upgraded/removed from the cluster, restart all nodes in the cluster (this can be a rolling restart).