fix: 9.3.0 shows storage as unknown and blocks dependent services

[goodcoffeecode]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When upgrading various Aspire packages from 9.2.1 to 9.3.0, Azure storage and cosmos DB containers and entities show as "unknown" in the dashboard.

Expected Behavior

I expected the dashboard to show the containers and entities as "Running"

Steps To Reproduce

My AppHost is targeting 9.2.1 for the following packages...

• Aspire.Hosting.AppHost
• Aspire.Hosting.Azure.CosmosDB
• Aspire.Hosting.Azure.Storage

When I run my app, I see all containers running in the dashboard.

Reproduction Steps

1. Upgrade either Aspire.Hosting.Azure.CosmosDB or Aspire.Hosting.Azure.Storage to 9.3.0
2. Ctrl+F5 to run the AppHost
3. Ctrl+C in the console to kill the process
4. Ctrl+F5 to run the AppHost

Now, in the dashboard, all the containers are "unknown"...

Reversion Steps

1. Revert package back to 9.2.1
2. Clean the solution
3. Ctrl+F5 to run the AppHost

Now, all containers are running again.

Impact

All the containers are actually running. However, if any of my apps WaitFor() those containers or entities, they themselves will never start.

Furthermore, when deployed to Azure, the dashboard shows no information about Cosmos DB or Azure Storage at all.

Workaround

Removing the WaitFor(), but leaving the WithReference() is sub-optimal, but the service do start and the app works as expected.

Exceptions (if any)

No exceptions.

.NET Version info

C# .NET 9

Anything else?

VS 2022 17.4

[davidfowl]

@goodcoffeecode can you share your apphost?

PS: I assume you are not using the emulator.

[davidfowl]

Furthermore, when deployed to Azure, the dashboard shows no information about Cosmos DB or Azure Storage at all.

Azure resources don't show up in the hosted ACA dashboard. This isn't a regression, just not implemented.

[goodcoffeecode]

Hi David,

Correct, I'm not running any of these with an emulator, They're pointed directly at Azure resources.

Thanks,

Chris

[goodcoffeecode]

AppHost (partial)...

using Azure.Provisioning.CosmosDB;

var builder = DistributedApplication.CreateBuilder(args);

var cosmosAuthdb = builder
    .AddAzureCosmosDB("cosmos-auth-db")
    .ConfigureInfrastructure(config =>
    {
        var account = config.GetProvisionableResources()
        .OfType<CosmosDBAccount>()
        .Single();

        // Make Cosmos DB serverless...
        account.Capabilities.Add(new CosmosDBAccountCapability
        {
            Name = "EnableServerless"
        });
    })
    .AddCosmosDatabase("entities");

var companies = cosmosAuthdb.AddContainer("companies", "/id");
var installers = cosmosAuthdb.AddContainer("installers", "/companyId");
var projects = cosmosAuthdb.AddContainer("projects", "/companyId");
var homeowners = cosmosAuthdb.AddContainer("homeowners", "/firstLetterOfEmail");

builder.AddProject<Projects.AuthorizationApi>("authorizationapi")
    .WithExternalHttpEndpoints()
    .WithReference(cosmosAuthdb)
    .WithReference(appInsights);
    //.WaitFor(cosmosAuthdb);    // Commented out otherwise won't start

builder.Build().Run();

[davidfowl]

OK I see the regression, it's in this PR #9147 we removed some code in the AzureProvisioner that propagates the state. We'll get this fixed in 9.3.1.

[goodcoffeecode]

Thanks David, really appreciate you looking into the issue.