Uninstalling Components
Select an uninstallation mode based on the installation mode.
Binary Mode
The following uses the Ascend Device Plugin as an example to describe how to uninstall a component. Uninstall other components by yourself.
- Log in to the node where the component is deployed as the root user.
- Run the following commands to uninstall the Ascend Device Plugin:
systemctl stop device-plugin.service systemctl disable device-plugin.service chattr -i /etc/systemd/system/device-plugin.service rm -f /etc/systemd/system/device-plugin.service systemctl daemon-reload systemctl reset-failed chattr -i /usr/local/bin/device-plugin rm -f /usr/local/bin/device-plugin rm -rf /usr/local/kmc
Deleting the /usr/local/kmc directory may affect the Ascend Device Plugin and NPU-Exporter components that are started in binary mode in the system. Exercise caution when deleting the directory.
Container Mode
The uninstallation methods of all components are similar. That is, go to the directory where the YAML configuration file of a component is located and delete the component. This operation needs to be performed on the Kubernetes master node. This section uses the HCCL-Controller as an example to describe how to uninstall a component. Uninstall other components by yourself.
- Log in to the master node as the root user.
- Go to the directory where the YAML configuration file of the HCCL-Controller is stored, for example, /home/ascend-hccl-controller.
cd /home/ascend-hccl-controller
- Run the following command to uninstall the HCCL-Controller:
kubectl delete -f hccl-controller-*.yaml
When the Ascend Device Plugin is used together with Volcano, a ConfigMap is created. Run the following command to delete the ConfigMap:
kubectl delete cm mindx-dl-deviceinfo-<node-name> -n kube-system