DVCS account webhook status stuck in the PENDING status
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When attempting to add a new DVCS account, the organization account webhook security remains stuck at the PENDING status.
Environment
Jira Data Center
Diagnosis
In the atlassian-jira.log, look for the following errors:
2024-06-04 08:39:00,913+0000 Caesium-1-2 DEBUG ServiceRunner [c.a.j.p.dvcs.service.OrganizationServiceImpl] Finding organization by ID [162]
2024-06-04 08:39:00,946+0000 Caesium-1-2 DEBUG ServiceRunner [c.a.j.p.dvcs.service.RepositorySyncServiceImpl] Syncing repositories for organization [xxxxx/xxxxx]
2024-06-04 08:39:00,950+0000 Caesium-1-2 DEBUG ServiceRunner [c.a.j.p.dvcs.service.RepositorySyncServiceImpl] Repository sync already in progress, ignoring request
2024-06-04 08:39:00,950+0000 Caesium-1-2 WARN ServiceRunner [c.a.j.p.d.scheduler.organizations.OrganizationRepoSyncJob] Organization xxxxx/xxxxx wasn't successfully syncedFor example, look for the keywords:
Repository sync already in progress, ignoring requestCause
The message indicate there's a cluster lock for that organization.
Solution
Please schedule a maintenance window to proceed with the following steps:
- Delete the problematic DVCS account.
- Wait until it is completely removed.
- Restart all the nodes one by one.