Could Not Add Host Error

[jacks4ever]

Where might I find help to this problem?

Despite running the script below to reset my installation of CloudStack 4.20.0 and reinstalling exactly to the Apache suggested installation instructions for KVM/Ubuntu, the same UUID keeps being populated for my agent. Where does CloudStack get the UUID from? When I manually run uuidgen on the command line of Ubuntu 24.04, and then update the agent, it just adds another one and then CloudStack Management gets confused. I would like for a clean install by understanding where this GUID could be cached, because I am removing everything I can think of where it might be stored.

Any assistance or pointers are greatly appreciated!

#!/bin/bash

Ensure the script is run with root privileges

if [ "$EUID" -ne 0 ]; then
echo "Please run as root or use sudo."
exit 1
fi

echo "Starting the Apache CloudStack teardown process..."
echo "Stopping Services..."
systemctl stop cloudstack-management
systemctl stop cloudstack-agent
systemctl stop cloudstack-usage

Tear down Apache CloudStack

echo "Step 1: Dropping existing CloudStack databases..."
mysql -uroot --password= -e "DROP DATABASE cloud; DROP DATABASE cloud_usage; DROP USER 'cloud'@'localhost'; FLUSH PRIVILEGES;"

echo "Step 2: Removing CloudStack packages..."
apt-get remove --purge -y cloudstack-management cloudstack-agent cloudstack-usage cloudstack-common libvirt-daemon qemu-kvm qemu-system libvirt-clients libvirt-daemon-system

echo "Step 3: Cleaning up CloudStack directories and files..."
rm -Rf /etc/cloudstack /var/lib/cloudstack /var/log/cloudstack /usr/share/cloudstack-agent /var/cache/cloudstack /usr/share/cloudstack-management /usr/share/cloudstack-usage /var/lib/libvirt /etc/libvirt

echo "Step 4: Removing unused dependencies..."
apt autoremove -y

echo "Step 5: Removing common CloudStack files..."
rm -Rf /usr/share/cloudstack-common

echo "Tear down process completed..."

[Pearl1594]

@jacks4ever Do you run this script every time there is a failure encountered in the zone setup phase? If yeas - then it is pretty odd that the host table still has details of the previous attempts of the hosts being added.