Check System Integrity Error

Hello,

We have following error in the integrety checks.

Task ID: ServerTasks-16386
Task status: Failed
Task queued: Thursday, July 13, 2017 4:48 PM
Task started: Thursday, July 13, 2017 4:48 PM
Task duration: less than a second
Server version: 3.13.10+Branch.master.Sha.fc73332b91b98afa44f1f88f66ba21d9c8e69b10
Server node: SF3DDAPP4

                | Failed: Check System Integrity

16:48:36 Info | Schema… [ Passed ]
16:48:36 Info | Release channel belongs to the appropriate project… [ Passed ]
16:48:36 Error | Orphaned tenanted deployments… [ Failed ]
16:48:36 Info | Orphaned channels… [ Passed ]
16:48:36 Info | Only one unfrozen deployment process per project… [ Passed ]
16:48:36 Fatal | One or more data errors were found.
|
| Failed: Orphaned tenanted deployments
16:48:36 Error | Showing top 20 of 35 errors:
| The deployment {Id: ‘Deployments-1368’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1432’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1506’, Name: ‘Deploy to Staging for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1524’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1527’, Name: ‘Deploy to Integration for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1530’, Name: ‘Deploy to Integration for MorningStar Old NonProduction (#2)’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1543’, Name: ‘Deploy to Staging for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1608’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1618’, Name: ‘Deploy to Staging for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1692’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1698’, Name: ‘Deploy to Integration for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1720’, Name: ‘Deploy to Staging for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1773’, Name: ‘Deploy to Staging for MorningStar Old NonProduction (#2)’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-1840’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2244’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2259’, Name: ‘Deploy to Dev for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2269’, Name: ‘Deploy to Dev for MorningStar Old NonProduction (#2)’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2282’, Name: ‘Deploy to Staging for MorningStar Old NonProduction’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2665’, Name: ‘Deploy to Dev for NonProduction MorningStar Old’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
| The deployment {Id: ‘Deployments-2682’, Name: ‘Deploy to Staging for NonProduction MorningStar Old’} belongs to Tenant Id ‘Tenants-167’ which does not exist.
|

Can you please advice how to solv this error.

Regards,
Vladi

Hi Vladi,

We previously had an issue where tenanted deployments were not deleted properly when the tenant was removed, leading to orphaned records. The issue was resolved in 3.13.8 but in some cases the orphaned records remain.

To remove them, you can execute the script provided in the “Workaround” section of the original issue: https://github.com/OctopusDeploy/Issues/issues/3101

Your integrity-check should then pass. Please don’t hesitate to ask if you have any issues with this, or have any further questions.

I hope that helps,
Michael