IT37880: REGISTRATION WITH IBM SPECTRUM PROTECT PLUS SERVER CAN NOT COMPLETE IF CLUSTER NODE IS IN NOTREADY STATE

APAR status

• Closed as program error.

Error description

• Registration of Openshift or kubernetes cluster with IBM
  Spectrum Protect Plus server can not complete if cluster node is
  in NotReady state at the time of registration.
  If your cluster is already registered with IBM Spectrum Protect
  Server and the cluster node used for registration becomes
  unavailable, backup and restore operations complete with error
  code CTGGA1666:
  
  Could not establish an SSH session with server on
  host(X.XX.XX.XX) at port(30,001).
  Error(java.net.ConnectException: Connection timed out
  (Connection timed out))
  
  Use 'kubectl get nodes' command to verify the status of cluster
  nodes:
  $ kubectl get nodes
  NAME                                                STATUS
  ROLES    AGE    VERSION
  doorknob73.scaleocp.dkcloud.local   NotReady   master   156d
  v1.20.0+2817867
  doorknob74.scaleocp.dkcloud.local   Ready        master   156d
  v1.20.0+2817867
  doorknob75.scaleocp.dkcloud.local   Ready        master   156d
  v1.20.0+2817867
  

Local fix

• Manually register your Openshift or kubernetes cluster in IBM
  Spectrum Protect Plus server. Specify IP address of any cluster
  node that is in Ready state.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus version 10.1.8                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see ERROR Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the fixing level when available. This problem is       *
  * currently projected to be fixed in IBM Spectrum Protect Plus *
  * level 10.1.9.                                                *
  * Note that this is subject to change at the discretion of IBM *
  ****************************************************************
  

Problem conclusion

• When registering with SPP server for the first time after
  initial product install, use IP address of the first available
  cluster node
  If cluster node used for registration becomes unavailable,
  re-register with SPP server using IP address of  the next
  available node.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• App      Kubernet
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels