Unhealthy Azure WebApps are not shown in the Environments tab

[deanmalone]

Unhealthy Azure WebApps are not displayed as expected under then 'Unhealthy' section on the Environments tab.

For example, on deploy3.octopushq.com, unhealthy targets are not showing up.

The following error is occurring on the browser:

Creating Octopus client for endpoint: https://deploy3.octopushq.com/
3angular.js:12314 Error: Cannot find module './Server-Unhealthy.AzureWebApp.png'.
at https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:21910:42
at webpackContextResolve (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:21910:90)
at webpackContext (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:21907:30)
at Object.calculateTargetIcon (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:2946:17)
at renderStatus (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32742:46)
at renderMachineList (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32699:26)
at update (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32721:33)
at ensureMachineList (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32725:18)
at render (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32732:18)
at link (https://deploy3.octopushq.com/application.0-53-9094886b8ab2b39.hashedasset.js:32779:14)

[droyad]

Some Unhealthy icons are missing. Been broken for at least 6 months, so I think we should wait until this screen is rewritten in 4.0

[droyad]

Obsolete if we remove them in #3806

[droyad]

Not removing them
https://trello.com/c/lVgclU76/494-icon-is-missing-for-unhealthy-azure-webapps

[droyad]

Release Note: Added an icon for Unhealthy Azure cloud services

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.