Summary

The following symptoms are observed:

• Mirror: any git operation fails with fatal: Authentication failed errors when performing any git operation
• Primary/Upstream: the application link overview page shows a "Non Atlassian" application link

Steps to Reproduce

1. Not available / currently under investigation

Expected Results

The mirror is always successfully working.

Actual Results

Git operations from the mirror fail while the primary/upstream is fully functional.

A unique set of log lines that can be related to this issue has not been identified yet, but in some instances the following logs have been identified in the primary:

ERROR [http-nio-7990-exec-20] addon_bitbucket.mirror.btuq-tz6u-2ty4-4nts *1H1PNVRx1279x5128x1 <request_ip> "PUT /rest/mirroring/latest/mirrorServers/BTUQ-TZ6U-2TY4-4NTS HTTP/1.1" c.a.p.c.p.l.ConnectAddonInstaller An exception occurred while installing the plugin '[bitbucket.mirror.btuq-tz6u-2ty4-4nts]. Restoring previous version...
java.lang.NullPointerException: null

Workaround

• Delete the "unexpected / non Atlassian" application link
• Delete the mirror from the UI
• Re-register the mirror with the primary
• Restart the mirror

Notes

In the versions 6.0.0, 5.14.3, 5.15.2, 5.16.1, 5.12.4, 5.13.4, 5.11.4 and 5.10.4 an hardening mechanism has been introduced to reduce the occurrence of these cases (in particular when two mirrors are trying to upgrade the connect add on at the same time). This, however, did not cover all the scenarios so the ticket has been reopened on the 18th of April.