Remove preserve file before calling prune_nodes #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
below scripys:
bash ./wipe/baremetal-lab-post-wipe-commands.sh
bash ./dns/baremetal-lab-post-dns-commands.sh
bash ./firewall/baremetal-lab-post-firewall-commands.sh
bash ./load-balancer/baremetal-lab-post-load-balancer-commands.sh
contains the following code snippet:
[ -z “${PULL_NUMBER:-}” ] &&
timeout -s 9 10m ssh “${SSHOPTS[@]}” “root@${AUX_HOST}”
test -f /var/builds/${NAMESPACE}/preserve &&
exit 0
which causes them to exit 0 early, due to the existence of preserve file, hence actual pruning will not happen
The PR propose to delete preserve file once a decision is taken to prune the cluster, before calling prune_nodes