Applying updates to the SAS^® Infrastructure Data Server (Crunchy Data PostgreSQL) results in a pod that stops responding. Messages similar to the following might appear in the log for the affected pod:

Update Procedure

To successfully apply updates, use the following procedure:

Important Note: 

• You must be an administrator with namespace permissions in order to perform the following steps.
• In the following steps, you must replace <cluster-name> with the cluster that you are working on: sas-crunchy-data-postgres, sas-crunchy-data-cpspostgres, or sas-crunchy-data-cdspostgres

1. To make it easier to perform these commands, you might want to make an alias:
   • alias kc='kubectl -n <namespace>'
2. Execute into the hanging primary pod:
   • kc exec -it <primary hanging pod> -- bash
3. Once in the pod, change directory to the data directory:
   • cd /pgdata
4. If the <cluster-name>.initializing file exists, then remove it. Note: The file might not exist.
   • Here is an example:
     • rm sas-crunchy-data-postgres.initializing
5. If this directory exists, <cluster-name>_[tmp or timestamp], then move it to make it the primary directory:
   • mv sas-crunchy-data-postgres_######## sas-crunchy-data-postgres
6. Change directory into the <cluster-name> now:
   • cd sas-crunchy-data-postgres
7. If any of the following files exist in the cluster directory, remove them:
   • rm standby.signal
   • rm recovery.signal
   • rm recovery.conf
8. Exit from the primary pod:
   • exit
9. Edit the clusters configuration map to make sure the 'init' value is set to 'false':
   • kc edit configmap <cluster-name>-pgha-config
   • Make sure that this is the value for init (and, if not, change it):
     • init: "false"
10. Scale down the cluster <cluster-name>:
    • kc scale --replicas=0 deploy sas-crunchy-data-postgres
11. Make sure the <cluster-name> secret still exists:
    • kc get secret sas-crunchy-data-postgres-tls-secret
12. If the <cluster name>-tls-secret does not exist, then download the cluster-name-postgres-tls.zip file to create a new one:
    • Download the cluster-name-postgres-tls.zip file to anywhere on your system and unzip it.
    • Edit cluster-name-postgres-tls.yaml to rename <cluster-name> in the file to the appropriate cluster name:
      • vi cluster-name-postres-tls-yaml
      • Change any reference in the file for <cluster-name> to sas-crunchy-data-postgres, sas-crunchy-data-cpspostgres, or sas-crunchy-data-cdspostgres.
      • Apply the file:
        • kc apply -f cluster-name-postgres-tls.yaml
13. Scale the <cluster-name> backup:
    • kc scale --replicas=1 deploy sas-crunchy-data-postgres
14. Ensure that the cluster comes back up:
    • kc get pods | grep -i postgres

For more information about SAS Viya software updates, see Getting Started with Updating Software in SAS^® Viya^® Operations.

Operating System and Release Information