airship/airshipctl
Code Issues Proposed changes

Changes gating scripts to use the airshipctl move command.

Browse Source 
Change-Id: I383343f4cde3aa3d431844f5792ee75d305d5210
This commit is contained in:
Arvinderpal Wander 2020-10-06 06:57:54 -07:00
parent 96e88e2523
commit e3065784ee
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
tools/deployment/33_cluster_move_target_node.sh
View File

@ -26,9 +26,8 @@ kubectl --kubeconfig $KUBECONFIG --context $KUBECONFIG_EPHEMERAL_CONTEXT get clu
echo "Annotate BMH for target node" echo "Annotate BMH for target node"
kubectl --kubeconfig $KUBECONFIG --context $KUBECONFIG_EPHEMERAL_CONTEXT annotate bmh node01 baremetalhost.metal3.io/paused=true kubectl --kubeconfig $KUBECONFIG --context $KUBECONFIG_EPHEMERAL_CONTEXT annotate bmh node01 baremetalhost.metal3.io/paused=true
# Switch to airshipctl phase clusterctl-move when it is working
echo "Move Cluster Object to Target Cluster" echo "Move Cluster Object to Target Cluster"
clusterctl --v 20 move --kubeconfig $KUBECONFIG --kubeconfig-context $KUBECONFIG_EPHEMERAL_CONTEXT --to-kubeconfig $KUBECONFIG --to-kubeconfig-context $KUBECONFIG_TARGET_CONTEXT airshipctl phase run clusterctl-move
echo "Waiting for pods to be ready" echo "Waiting for pods to be ready"
kubectl --kubeconfig $KUBECONFIG --context $KUBECONFIG_TARGET_CONTEXT wait --all-namespaces --for=condition=Ready pods --all --timeout=3000s kubectl --kubeconfig $KUBECONFIG --context $KUBECONFIG_TARGET_CONTEXT wait --all-namespaces --for=condition=Ready pods --all --timeout=3000s