Backup and restore fails in Data Virtualization

After you run a backup and restore, you might encounter a transport: authentication handshake failed: x509: certificate signed by unknown authority message in which pods are in a crash or restart loop.

Symptoms

You see Data Virtualization pods, such as the head and hurricane pods, in a crash or restart loop as shown in the following example.

c-db2u-dv-db2u-0                          1/1     Running   2          164m
c-db2u-dv-db2u-1                          1/1     Running   0          164m
c-db2u-dv-dvapi-74df7cbfdc-pbcx8          1/1     Running   6          164m
c-db2u-dv-dvcaching-955c64d9c-r6gdn       1/1     Running   1          164m
c-db2u-dv-dvutils-0                       1/1     Running   0          164m
c-db2u-dv-hurricane-dv-58b5f96584-bh8dk   1/2     Running   6          164m

Run the following command from the pods that are failing.

$ oc exec -i c-db2u-dv-db2u-0 -n zen -c db2u -- bash -c 'db2uctl markers list'

You see an error message that is similar to the following example.

Error: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority (possibly because of \"RSA_verify failed\\nopenssl error(s):\\nerror:0407008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid

Resolving the problem

Run sv restart /etc/service/db2uapi as the db2uadm user in each Data Virtualization pod to restart db2uapi. For more information about Data Virtualization pods, see Preparing to install Data Virtualization.