group normalisation from 4.0 upgrade tasks is breaking permissions

Group normalisation from 4.0 upgrade tasks is breaking permissions. Scenario:

• backup created for 3.1.7 instance, repo "repo-uppercase-access" configured with "GROUP-A" can read access
• backup file restored on 4.1 instance, I can see following messages in the upgrade log

  $ grep -i renam /tmp/restore.out
  INFO  - The group Global-Group-A has a duplicate name. Will rename the group to Global-Group-A_migration1
  INFO  - The group Group-A has a duplicate name. Will rename the group to Group-A_migration1
  INFO  - The group GROUP-A has a duplicate name. Will rename the group to GROUP-A_migration2

  on 4.1 instance repository "repo-uppercase-access" is configured so "GROUP-A" can read. There should be "GROUP-A_migration2" instead

Workaround

To address this problem, please refer to the FishEye 4.0 group name normalization page for instructions.