Disaster Recovery
#
App service stops workingPerform these steps when no Hub pages are loading and you are receiving server level errors.
In production, the Hub app service is geo-redundant. The West US instance is used primarily, but if it fails, the East US instance is switched to by the traffic manager.
- Navigate to the affected web server app service in the Azure App Portal. See the list of services for links to each
- Press
Restart
and confirm the restart - Wait for the completion of the app service restart and then verify the service is running by opening Hub in the corresponding environment
#
App not working correctly or not foundPerform these steps when Hub is working properly but an individual application is not. This the recommended contingency plan when deploying an application.
#
Apps released through TeamCity- Navigate to the application's entry in TeamCity
- Select
Deploy to X
where X in the affected environment - Find the artifact used by the previously known working build a note this for later. Eg.
#1.6.2.225
- The artifact build number is noted under the arrow next to
x artifact depedency change
- The artifact build number is noted under the arrow next to
- Select
...
next toRun
- Under
Dependencies
select the artifact previously identified - Select
Run Build
- Wait for the deployment to finish and then confirm it is working by opening the application in Hub
#
Apps released through Azure DevOps- Navigate to the application's entry in Azure DevOps
- Applications will commonly be under their owning team's project. This can be found in BirdBrain
- Select
Pipelines > Pipelines
- Select the application you want to deploy
- Select the previously know working run
- Select
Rerun stage
in the affected environment - Wait for the stage to complete and then confirm it is working by opening the application in Hub
#
Sidebar is not displaying entriesPerform these steps when the Hub sidebar has no applications listed in it. This has been cause by an improperly formatted applications.json
- Navigate to application.json release pipeline
- Select a the most recent known working release
- Under the affected environment, select
Redeploy
- Wait for the deployment to finish and then confirm it is working by opening Hub