IBM Support

Cloud Pak for Security: Shutdown Procedures

How To


Summary

What are the steps for a graceful shutdown of Cloud Pak for Security (CP4S)?

Objective

Not following these instructions increases the probability of critical issues bringing the Cluster back online.
Typical reasons for requiring a complete Cluster Shutdown include but are not limited by:
  • Server maintenance
  • Planned power outage or unplanned battery backup enabled
  • Work that requires the server hosts to be powered off

Steps

Note: If you are not willing to restore the Cluster, do not shut it down.
  1. Log in to the Red Hati OpenShifti Cluster:
    oc login -u ADMIN https://CONSOLE:PORT
    NOTE: Replace ADMIN with your admin user, and replace CONSOLE and PORT with your server-specific information.
  2. Verify nodes are in Ready status:
    oc get nodes
  3. Validate all Cluster Operators are all available True and degraded False:
  4. oc get clusteroperators
  5. Check etcd for the controller nodes:
    oc get pods -n openshift-etcd | grep -v etcd-quorum-guard | grep etcd
    NOTE: Validate that all of the etcd pods are 3/3 and running.
  6. Select the first etc node from previous step:
    oc rsh -n openshift-etcd etcd-cp4s-lab-control-1
    NOTE: replace openshift-etcd and etcd-cp4s-lab-control-1 with the values appropriate for your environment.
  7. Validate that etcd is in sync and there are no issues:
    etcdctl member list -w table
  8. Make an etcd backup.
  9. Make a CP4S backup.
  10. Initiate the Graceful Shutdown of the Red Hati OpenShifti Cluster.
    NOTE: Do NOT force the shutdown. Stopping the nodes can take time.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"a8m3p0000000rbnAAA","label":"Support-\u003EAdministration Task"}],"ARM Case Number":"TS018859401","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
03 April 2025

UID

ibm17230040