Unresponsive clouds cause delay in "accepted" to "creating" transition

prominence-eosc / imc

PROMINENCE infrastructure provisioner

Apache License 2.0

0 stars 0 forks source link

Unresponsive clouds cause delay in "accepted" to "creating" transition #34

Closed alahiff closed 5 years ago

alahiff commented 5 years ago

If a cloud is unresponsive (e.g. due to scheduled work), jobs seems to stay in the "created" state for a long time before changing to "deploying". The IMC state stays in "accepted" for a long time before changing to "creating".

alahiff commented 5 years ago

Fixed in https://github.com/prominence-eosc/imc/commit/438bcae9eb2519d56cf31b9d3911914b270cd77e. The state change was happening after initial steps of deployment (cloud quotas, flavours & images updates), and it was these steps that were taking too long. Changed to happen at the very beginning of deployment, as this makes the most sense in fact.