From 0e38cc08638c998b9cf60ccb95e44f9d98e8f27e Mon Sep 17 00:00:00 2001
From: Kostiantyn Kalynovskyi <kkalinovskiy@gmail.com>
Date: Wed, 26 May 2021 00:51:54 +0000
Subject: [PATCH] Remove redundant waiting logic for BMHs

Waiting for BMH to become ready isn't needed because we wait for
node to become ready anyway. It is not guaranteed that BMH will
ever reach provisioning state ready, because this status is
intermediate.

Change-Id: Ia3a9e41daaf759dbb48dd7d615bf993b1831f1d1
---
 tools/deployment/35_deploy_worker_node.sh | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/tools/deployment/35_deploy_worker_node.sh b/tools/deployment/35_deploy_worker_node.sh
index 005966626..10194ddd8 100755
--- a/tools/deployment/35_deploy_worker_node.sh
+++ b/tools/deployment/35_deploy_worker_node.sh
@@ -23,12 +23,6 @@ airshipctl phase run virsh-destroy-vms --debug
 echo "Deploy worker node"
 airshipctl phase run workers-target --debug
 
-# Waiting for bmh to be in ready state
-# Scripts for this phase placed in manifests/function/phase-helpers/wait_bmh/
-# To get ConfigMap for this phase, execute `airshipctl phase render --source config -k ConfigMap`
-# and find ConfigMap with name kubectl-wait-bmh
-airshipctl phase run kubectl-wait-bmh-target --debug
-
 # Waiting for node to be provisioned."
 # Scripts for this phase placed in manifests/function/phase-helpers/wait_label_node/
 # To get ConfigMap for this phase, execute `airshipctl phase render --source config -k ConfigMap`