airship/airshipctl
Code Issues Proposed changes

Remove redundant waiting logic for BMHs

Browse Source 
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
This commit is contained in:
Kostiantyn Kalynovskyi 2021-05-26 00:51:54 +00:00
parent 9f4b5b82bd
commit 0e38cc0863
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tools/deployment/35_deploy_worker_node.sh
View File

@ -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`