After Deauthorizing Hypervisor Hosts, How to Ensure That The Host is Not in a "Waiting to be Authori

Problem

After deauthorizing hypervisor hosts in U/I, how to ensure the host is not seen to be in a " waiting to be authorized" state.

Environment

• Platform9 Managed OpenStack - All Versions

• Platform9 Managed Kubernetes - All Versions

Procedure

Remove all Platform9 packages which would still be present on the hosts in the customer's infrastructure.

1. List the packages.

For Ubuntu:

None

dpkg -l | grep pf9

For Centos:

None

rpm -qa | grep pf9

1. Remove/purge all the pf9 packages from the host.

For Ubuntu:

None

# dpkg --remove --force-remove-reinstreq <pf9-packagename>
# dpkg --purge --force-all <pf9-packagename>

For CentOS:

None

# yum remove [pf9-packagename]

OR

None

# yum erase [pf9-packagename]

1. Ensure that the following directories have been removed after the removal of the packages.

None

rm -rf /var/opt/pf9
rm -rf /var/log/pf9
rm -rf /opt/pf9
rm -rf /etc/pf9

Additional Information

Deauthorize a Host