-
Notifications
You must be signed in to change notification settings - Fork 190
/
host_cleanup.sh
executable file
·85 lines (73 loc) · 2.82 KB
/
host_cleanup.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
#!/usr/bin/env bash
set -x
source logging.sh
source common.sh
source utils.sh
source validation.sh
early_cleanup_validation
if [ -z "${METAL3_DEV_ENV}" ]; then
export REPO_PATH=${WORKING_DIR}
sync_repo_and_patch metal3-dev-env https://github.com/metal3-io/metal3-dev-env.git
fi
export ANSIBLE_FORCE_COLOR=true
ansible-playbook \
-e @vm_setup_vars.yml \
-e "ironic_prefix=${CLUSTER_NAME}_" \
-e "cluster_name=${CLUSTER_NAME}" \
-e "provisioning_network_name=${PROVISIONING_NETWORK_NAME}" \
-e "baremetal_network_name=${BAREMETAL_NETWORK_NAME}" \
-e "working_dir=$WORKING_DIR" \
-e "num_masters=$NUM_MASTERS" \
-e "num_workers=$NUM_WORKERS" \
-e "num_extraworkers=$NUM_EXTRA_WORKERS" \
-e "virthost=$HOSTNAME" \
-e "manage_baremetal=$MANAGE_BR_BRIDGE" \
-e "nodes_file=$NODES_FILE" \
$ALMA_PYTHON_OVERRIDE \
-i ${VM_SETUP_PATH}/inventory.ini \
-b -vvv ${VM_SETUP_PATH}/teardown-playbook.yml
sudo rm -rf /etc/NetworkManager/dnsmasq.d/openshift-${CLUSTER_NAME}.conf /etc/yum.repos.d/delorean*
sudo rm -rf /etc/NetworkManager/conf.d/dnsmasq.conf
sudo rm -rf /etc/NetworkManager/dnsmasq.d/upstream.conf
if systemctl is-active --quiet NetworkManager; then
sudo systemctl reload NetworkManager
else
sudo systemctl restart NetworkManager
fi
# handle upgrade from legacy network scripts
for interface in ${PROVISIONING_NETWORK_NAME} ${BAREMETAL_NETWORK_NAME} ${PRO_IF} ${INT_IF}; do
interface_config=/etc/sysconfig/network-scripts/ifcfg-${interface}
if [ -e $interface_config ]; then
sudo rm -f $interface_config
IF_FOUND=true
fi
done
if [ "${IF_FOUND:-}" == "true" ]; then
sudo systemctl restart network.service
fi
# There was a bug in this file, it may need to be recreated.
# delete the interface as it can cause issues when not rebooting
if [ "$MANAGE_PRO_BRIDGE" == "y" ]; then
sudo nmcli con del ${PROVISIONING_NETWORK_NAME} || true
sudo ip link delete ${PROVISIONING_NETWORK_NAME} || true
if [[ -d /sys/class/net/pro-ipv6-dummy ]]; then
sudo ip link delete pro-ipv6-dummy || true
fi
sudo rm -f /etc/NetworkManager/system-connections/${PROVISIONING_NETWORK_NAME}.nmconnection
fi
# Leaving this around causes issues when the host is rebooted
# delete the interface as it can cause issues when not rebooting
if [ "$MANAGE_BR_BRIDGE" == "y" ]; then
sudo nmcli con del ${BAREMETAL_NETWORK_NAME} || true
sudo ip link delete ${BAREMETAL_NETWORK_NAME} || true
if [[ -d /sys/class/net/bm-ipv6-dummy ]]; then
sudo ip link delete bm-ipv6-dummy || true
fi
sudo rm -f /etc/NetworkManager/system-connections/${BAREMETAL_NETWORK_NAME}.nmconnection
fi
# Drop all ebtables rules
sudo ebtables --flush
# Kill any lingering proxy
sudo pkill -f oc.*proxy
# Remove image-reg nfsshare
sudo rm -rf /etc/exports.d/dev-scripts.exports /opt/dev-scripts/nfsshare