Azure-docs: Health Probes don't work in V2

Created on 4 Feb 2019 · 8Comments · Source: MicrosoftDocs/azure-docs

I've seen multiple reports of Backend health not working with v2, even with the correct NSG ports opened and experienced it myself. All probes report "Unable to retrieve health status data. Check presence of NSG blocking ports".
Please add to known issues as until these work v2 is useless.

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: faa5b8a2-11a1-6a2d-07cb-ffcf39643ed4
Version Independent ID: 298a134e-fb27-f16d-bff2-d43eb0f766fd
Content: Autoscaling and Zone-redundant Application Gateway in Azure (Public Preview)
Content Source: articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

application-gatewasvc assigned-to-author product-issue triaged

Source

OffColour

Most helpful comment

I haven't found a solution, I've found a bug.

OffColour on 7 Feb 2019

😄2 👍2

All 8 comments

@OffColour Thanks for your feedback. We are currently looking in to it and will update you soon.

SubhashVasarapu-MSFT on 4 Feb 2019

I've found the source of the problem.
If the host name of any Listener is greater than 46 characters, the Backend Health blade stops working and reports "Unable to retrieve health status data" for all Probes.

OffColour on 7 Feb 2019

@OffColour Glad that you have found the solution for this issue and thanks for sharing the solution that worked for you. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

SubhashVasarapu-MSFT on 7 Feb 2019

I haven't found a solution, I've found a bug.

OffColour on 7 Feb 2019

😄2 👍2

@OffColour I have assigned the issue to the content author for further investigation.

SubhashVasarapu-MSFT on 7 Feb 2019

@OffColour
According to the product team, this might be a bug in the health status report mechanism, but more investigation is needed. Please open a support case. Send us the ticket number so we can forward to the product team to track.

vhorne on 4 Apr 2019

@vhorne Hi, I raised a support case, but because it's in preview with no support they didn't really do anything with it. Is there a proper bug reporting mechanism for products in preview/beta?

OffColour on 5 Apr 2019

@OffColour

This has been fixed. v2 was released to GA today, so it should work now.