Anyone have issues with hanging when trying to create a `Man

Question

Anyone have issues with hanging when trying to create a `ManagedEnvironment` for ContainerApp Using `AzureNative` basically example from the docs The env gets created but pulumi hangs

clever-sunset-76585 · Answer

Hmm I haven t had that problem I recently set one up

bored-activity-40468 · Answer

Thanks that s helpful it must be something I m doing probably something silly slightly smiling face

clever-sunset-76585 · Answer

Can you repro it consistently

bored-activity-40468 · Answer

so far yeah but I m going to make a new project with only creating that resource and not using automation api an verify that works

bored-activity-40468 · Answer

yeah even with hello world ManagedEnvironment env gets created and pulumi hangs Running again with verbosity cranked up

clever-sunset-76585 · Answer

Ah you are using the dotnet runtime Mine was Node js

bored-activity-40468 · Answer

yeah I can try it with another runtime

clever-sunset-76585 · Answer

I wonder if there is some process teardown that is holding up Pulumi after resources have been created

bored-activity-40468 · Answer

That s what it seems like its not getting the I m done acknowledgement and timing out

clever-sunset-76585 · Answer

Verbose logs should help diagnose what s holding up Pulumi

bored-activity-40468 · Answer

Tried with 2022 06 01 preview and it doesn t hang but blows up which is progress slightly smiling face ` Code= OperationFailed Message= Managed environment failed to initialize due to managed cluster provision failed `

bored-activity-40468 · Answer

env gets created though

clever-sunset-76585 · Answer

Yikes Fwiw I used the default API version that Pulumi has locked that resource to

bored-activity-40468 · Answer

Adding custom timeouts found them here <https github com jchannon pulumirepro blob 1ba4bc0a4dc9c7f18ffe1aa01bd2202415e72cd7 src container apps Program cs L105> seems to fix it

clever-sunset-76585 · Answer

That s good but it shouldn t be needed here since it seems Pulumi isn t waiting on Azure in this case I would still open an issue and mention your workaround

bored-activity-40468 · Answer

I was mistaken time out didn t do anything but I think the whole issue is related to an azure keyvault outage

clever-sunset-76585 · Answer

oh interesting are you using KV as your secrets provider

bored-activity-40468 · Answer

No but the outage had ContainerApps listed as being effected Just ran my hello world for this and it worked without issue thanks for the help and feedback slightly smiling face