Distinguish component unreadiness from check readiness failure
Closed this issue · 1 comments
cliffano commented
For checking environment readiness, we have to set a delay for a period of time (currently 1 minute) before executing readiness check. This is due to the fact that the component (currently orchestrator) that performs the readiness check might not be ready yet.
This 1 minute delay needs to be eliminated, it would be good if it's possible to identify the component unreadiness (i.e. the orchestrator not in service) and then translate that to a pending state as event status.
This way the check readiness event naturally waits while it's pending the component readiness in order to be able to check the environment readiness.
cliffano commented
Done. Included in v1.3.1 .