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:

Kubernetes and OpenShift

  1. Access web master pod
  2. Navigate to patch directory:  cd patch/
  3. Remove a patch: rm <patch.file.name>
  4. Exit the web master pod: exit
  5. Run a get pods command
    • OpenShift: oc get pods -n <MI namespace>
    • Kubernetes: kubectl get pods -n <MI namespace>
  6. Delete web master and web 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> 
  7. New web master and web slave pods are automatically recreated and the patch is successfully removed

Docker Swarm or Amazon ECS

  1. Access web master container
  2. Navigate to patch directory: cd patch/
  3. Remove a patch: rm <patch.file.name>
  4. Exit the web master container: exit
  5. Run docker ps command to list the running containers
  6. Delete the web master and web slave containers: docker rm <web master container id>, docker rm <web slave container id>
  7. New web master and web slave pods are automatically recreated and the patch is successfully removed

Simple Install

  1. SSH to the MI app server
  2. Access web container: mi-web
  3. Navigate to patch directory: cd patch/
  4. Remove a patch: rm <patch.file.name>
  5. Re-create the web container: mi-control up -d --force-recreate web
  6. New web container is launched and the patch is successfully removed