dimberman commented on a change in pull request #9332:
URL: https://github.com/apache/airflow/pull/9332#discussion_r440971538
##########
File path: scripts/ci/libraries/_kind.sh
##########
@@ -392,9 +397,9 @@ function wait_for_airflow_pods_up_and_running() {
echo "------- Running kubectl get pods: $i -------"
PODS=$(kubectl get pods --cluster "${KUBECTL_CLUSTER_NAME}" | awk
'NR>1 {print $0}')
echo "$PODS"
- NUM_AIRFLOW_READY=$(echo "${PODS}" | grep airflow | awk '{print $2}' |
grep -cE '([0-9])\/(\1)' \
+ NUM_AIRFLOW_READY=$(echo "${PODS}" | grep airflow | awk '{print $2}' |
grep -cE '([2-9])\/(\1)' \
| xargs)
- NUM_POSTGRES_READY=$(echo "${PODS}" | grep postgres | awk '{print $2}'
| grep -cE '([0-9])\/(\1)' \
+ NUM_POSTGRES_READY=$(echo "${PODS}" | grep postgres | awk '{print $2}'
| grep -cE '([1-9])\/(\1)' \
Review comment:
Before we would move on before the pods were actually ready. So if the
scheduler starts up with 0/2, it would say "ok that's good enough". this makes
the function hang until "2/2" are ready for the airflow pod and "1/1" is ready
for postgres.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
