This article describes the algorithm of rolling back a patch inside the web container.
To roll back a patch which is located inside the other container, execute the same commands simply replacing web  (for Simple Install) or web master, web slave (for Orchestrated Environments) with the name of container where the patch is located.
Table of contents:
NOTES:
- For details on applying a patch, see Applying Hot Fixes with the Patcher.
- Some patches cannot be reverted, such as patches with database migrations. Contact support@metricinsights.com to check if a patch is reversible.
Kubernetes and OpenShift
- Access web masterpod
- Navigate to patchdirectory:cd patch/
- Remove a patch: rm <patch.file.name>
- Exit the web masterpod:exit
- Run a get pods command - OpenShift: oc get pods -n <MI namespace>
- Kubernetes: kubectl get pods -n <MI namespace>
 
- OpenShift: 
- Delete web masterandweb slavepods:- OpenShift: oc delete pod <web master pod ID>,oc delete pod <web slave pod ID>
- Kubernetes: kubectl delete pod <web master pod ID>,kubectl delete pod <web slave pod ID>
 
- OpenShift: 
- New web masterandweb slavepods are automatically recreated and the patch is successfully removed
Docker Swarm or Amazon ECS
- Access web mastercontainer
- Navigate to patchdirectory:cd patch/
- Remove a patch: rm <patch.file.name>
- Exit the web mastercontainer:exit
- Run docker pscommand to list the running containers
- Delete the web masterandweb slavecontainers:docker rm <web master container id>,docker rm <web slave container id>
- New web masterandweb slavepods are automatically recreated and the patch is successfully removed
Simple Install
- SSH to the MI app server
- Access webcontainer:mi-web
- Navigate to patchdirectory:cd patch/
- Remove a patch: rm <patch.file.name>
- Exit the webcontainer:exit
- Re-create the webcontainer:mi-control up -d --force-recreate web
- New webcontainer is launched and the patch is successfully removed