[WebToolsE2E][Aspire] The endpoint for 'functionapp1' displays 'Hmmm...can't reach this page' when running Aspire Starter 9.2 with an Azure Functions project.

[vmykagapuz]

REGRESSION INFO

1. Worked in Aspire 9.1.0

INSTALL STEPS

1. Clean machine: Win11 x64 24h2 ENU
2. Install VS 17.13.5
3. Add dotnet9 feed for 9.2.0-preview.1
4. Install the latest Aspire 9.2.0-preview.1 templates
   dotnet new install Aspire.ProjectTemplates::9.2.0-preview.1.25201.19 --force
5. Install Docker Desktop

NOTE

1. This issue does not reproduce in 8.0 framework

REPRO STEPS

1. New project > .NET Aspire Starter App > .NET 9.0 > .NET Aspire version (9.2) > Create
2. Right click solution > Add > New Project > Azure Functions > .NET 9.0 Isolated > Check 'Enlist in .NET Aspire orchestration' > Create
3. Build and F5
4. Click the endpoint for 'functionapp1' project

ACTUAL
The page displays 'Hmmm...can't reach this page'

EXPECTED
The page should display 'Your Functions 4.0 app is up and running'

[davidfowl]

Did you look at the logs?

[vmykagapuz]

Did you look at the logs?

May I know where to check the logs for this issue?

[davidfowl]

These buttons should show the console logs for a resource:

[vmykagapuz]

This is the logs for functionapp1 after navigating to the endpoint

[davidfowl]

Is it possible that you just hit the url too early before the functions app is healthy?

[vmykagapuz]

Tried to check the health state first before clicking the endpoint and its Healthy.

[davidfowl]

There are no health checks on the functions project resource, so healthy in this case means the app is running.

[v-elenafeng]

@davidfowl @balachir This doesn't look like a specific issue with .net9, and it‘s also reproduced with .net 8 target (unlike mentioned in the bug note), where we can see the function app by navigating to [http://localhost:7071/api/Function1 instead of the endpoint in the dashboard.

But when aspire is not introduced, the port it actually runs on is the port given in launch.settings.json.

[davidfowl]

Moving this out of 9.2 I think the fix here is to add an http health check to functions projects (likely the template).

[balachir]

@davidfowl @v-elenafeng I investigated this some more and there seems to be a regression with Functions + Aspire scenario in Aspire 9.2 compared to Aspire 9.1. I found clearer repro steps and opened a separate issue #8589, which we may want to fix for 9.2.

I'll close this one as a dupe of that one.

@vmykagapuz