The upgrade of CP4S from 1.10.3 to 1.10.4 requires the Foundational Services to be at the Long Time Service Release, which is the channel v3.

If your deployment has Foundational Services beyond v3.19.4, you need to roll back following the instructions on https://www.ibm.com/docs/en/cloud-paks/cp-security/1.10?topic=it-rolling-back-foundational-services-fails-when-upgrading-from-1103-1104-by-using-red-hat-openshift-web-console

Symptoms

1. On IBM Cloud with Red Hat OpenShift Container Platform v4.8.50 and CP4S v1.10.3->1.10.4 upgrade. We followed the rollback steps and successfully rolled back Foundational Services to LTSR in both the cp4s and ibm-common-services namespaces. However, something went wrong and the login page came up blank. There was a successful HTML page returned, but the code was incomplete and as a user, you couldn't get past the cp-console login. The issue resolved itself.
2. After launch of the upgrade through the web interface you might see an error message:You can resolve it by

   oc edit subscription ibm-cp-security-operator

   
   Example output:

   ..    
   19 spec:
   20   channel: v1.10
   21   installPlanApproval: Automatic
   22   name: ibm-cp-security-operator
   23   source: cp4s
   24   sourceNamespace: openshift-marketplace
   25   startingCSV: ibm-cp-security-operator.v1.10.4
   26 status:
   ..

   If under 'spec:' you find this line

     startingCSV: ibm-cp-security-operator.v1.10.4

   You need to remove the 'startingCSV:' line completely before the rollback of the foundational services to the Long Time Service Release.

   oc exec deploy/cp-serviceability -- /opt/bin/cs_rollback -f --channel v1.10 $(oc whoami -t) ${NAMESPACE} ibm-common-services