BUG? Redeploy of existing working solution fails with resource timeout

Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.

MIT License

82 stars 12 forks source link

BUG? Redeploy of existing working solution fails with resource timeout #255

Open MickBadran opened 6 years ago

MickBadran commented 6 years ago

I had a previously working solution up for a few days and then it failed.

I then redeployed from VSNET which timedout and failed after 2.5hrs (which I tried 5 times - clean build, redeploy etc)

I then deleted all my SF artifacts and then redeployed and it worked!!!

Yay!!!

Q. Was there an environment upgrade? (if so - where could I find this information so I could just go straight to delete and redeploy stage)

Have a good one,

Mick.

mikkelhegn commented 5 years ago

There is some allocation logic in the service today that can put you on different deployment clusters / paths and might explain why this happened, but without specific resource-ids, region info and time it's hard to tell exactly what hit you :-)

We are however continuously updating the service @mattrowmsft