You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
For example if the kabanero-registry pod fails to start, then this loop will alternate between CONNECTING and TRANSIENT_FAILURE forever.
There should be a timeout on the loop - a maximum number of times it can iterate for example, so that the install will fail rather than hanging forever in this case.
The text was updated successfully, but these errors were encountered:
This has been requested before. We've generally punted on it because the install time of components can be non-deterministic, and the particular case of the registry state returning ready in a reasonable amount of time seems to be a bug in OLM, which we've made attempts at working around.
Users can make use of the bash timeout command if they want to exit an install that does not finish in a specified amount of time. set +x has long been the default for the script, so it's clear where a problem may be occurring.
https://github.com/kabanero-io/kabanero-operator/blob/master/deploy/install.sh#L223 will loop forever if the kabanero-catalog has a problem and never reaches READY state.
For example if the kabanero-registry pod fails to start, then this loop will alternate between CONNECTING and TRANSIENT_FAILURE forever.
There should be a timeout on the loop - a maximum number of times it can iterate for example, so that the install will fail rather than hanging forever in this case.
The text was updated successfully, but these errors were encountered: