Removing a Patch
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 [email protected] to check if a patch is reversible.
Kubernetes and OpenShift
- Access
web master
pod - Navigate to
patch
directory:cd patch/
- Remove a patch:
rm <patch.file.name>
- Exit the
web master
pod:exit
- Run a get pods command
- OpenShift:
oc get pods -n <MI namespace>
- Kubernetes:
kubectl get pods -n <MI namespace>
- OpenShift:
- Delete
web master
andweb slave
pods:- 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 master
andweb slave
pods are automatically recreated and the patch is successfully removed
Docker Swarm or Amazon ECS
- Access
web master
container - Navigate to
patch
directory:cd patch/
- Remove a patch:
rm <patch.file.name>
- Exit the
web master
container:exit
- Run
docker ps
command to list the running containers - Delete the
web master
andweb slave
containers:docker rm <web master container id>
,docker rm <web slave container id>
- New
web master
andweb slave
pods are automatically recreated and the patch is successfully removed
Simple Install
- SSH to the MI app server
- Access
web
container:mi-web
- Navigate to
patch
directory:cd patch/
- Remove a patch:
rm <patch.file.name>
- Exit the
web
container:exit
- Re-create the
web
container:mi-control up -d --force-recreate web
- New
web
container is launched and the patch is successfully removed