This message was deleted.
# azure
s
This message was deleted.
c
Hmm I haven't had that problem. I recently set one up.
b
Thanks, that's helpful, it must be something I'm doing, probably something silly 🙂
c
Can you repro it consistently?
b
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.
👍 1
yeah, even with hello world ManagedEnvironment, env gets created and pulumi hangs. Running again with verbosity cranked up.
c
Ah you are using the dotnet runtime. Mine was Node.js.
b
yeah, I can try it with another runtime
c
I wonder if there is some process teardown that is holding up Pulumi after resources have been created.
b
That's what it seems like, its not getting the, "I'm done" acknowledgement and timing out.
c
Verbose logs should help diagnose what's holding up Pulumi.
👍 1
b
Tried with 2022-06-01 preview and it doesn't hang but blows up, which is progress 🙂
* Code="OperationFailed" Message="Managed environment failed to initialize due to managed cluster provision failed"
env gets created though
c
Yikes! Fwiw, I used the default API version that Pulumi has locked that resource to.
👍 1
b
c
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.
b
I was mistaken, time-out didn’t do anything but I think the whole issue is related to an azure keyvault outage.
c
oh interesting...are you using KV as your secrets provider?
b
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. 🙂
👍 1