Troubleshooting
Problem
IBM Maximo Application Suite ("MAS") requires installing as a prerequisite the Service Binding Operator ("SBO"). But the latest versions of SBO (whether installed from the command line or from the OpenShift interface) install a version that is incompatible with MAS 8.4.x or 8.5.x.
Symptom
If SBO 0.9 or later is installed, when an application installation goes to create a service binding, the following error can occur:
Message: Failed to apply object: b’{"kind”:"Status”,"apiVersion”:"v1","metadata”:{},"status”:"Failure”,"message”:"ServiceBinding.binding.operators.coreos.com \\"<binding-name>\\” is invalid: spec.application: Required value”,"reason”:"Invalid”,"details”:{"name”:"<binding-name>”,"group”:"binding.operators.coreos.com”,"kind”:"ServiceBinding”,"causes”:[{"reason”:"FieldValueRequired”,"message”:"Required value”,"field”:"spec.application”}]},"code”:422}\n’
Cause
Service-Binding-Operator 0.9 introduced a behavior change that is incompatible with Maximo Application Suite.
Resolving The Problem
Uninstall Instructions: if Service Binding Operator 0.9.0 or later was already installed, uninstall the operator:
- Log in to the OpenShift interface as an Administrator
- Go to Operators --> OperatorHub and search for "Service Binding". It should return the Service Binding Operator you have installed.
- If the version displayed for Service Binding Operator shows "0.9.0" or later, select that Service Binding Operator icon. In the panel that results, there should be an "Uninstall" button at the upper left. Click that to uninstall Service Binding Operator. This will prompt you to make sure you want to remove this operator from all namespaces. Click "Uninstall" to continue.
Install Instructions: Installing Service Binding Operator 0.8 on a cluster for MAS 8.4.x or 8.5.x:
- Log in to the OpenShift cluster by using the oc login command
- Create a file called sbo.yaml that contains the following:
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: rh-service-binding-operator
namespace: openshift-operators
spec:
channel: preview
name: rh-service-binding-operator
source: redhat-operators
sourceNamespace: openshift-marketplace
installPlanApproval: Manual
startingCSV: service-binding-operator.v0.8.0
kind: Subscription
metadata:
name: rh-service-binding-operator
namespace: openshift-operators
spec:
channel: preview
name: rh-service-binding-operator
source: redhat-operators
sourceNamespace: openshift-marketplace
installPlanApproval: Manual
startingCSV: service-binding-operator.v0.8.0
- Apply that file: oc apply -f sbo.yaml
- Find the install plan:
installplan=$(oc get installplan -n openshift-operators | grep -i service-binding | awk '{print $1}'); echo "installplan: $installplan"
- Approve the install plan:
oc patch installplan ${installplan} -n openshift-operators --type merge --patch '{"spec":{"approved":true}}'
- The oc patch command should return the following output:
installplan.operators.coreos.com/<install_plan_name> patched
Where <install_name_plan> is the actual install plan name.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000GoLBAA0","label":"Maximo Application Suite->Installation"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.4.0;8.5.0"}]
Was this topic helpful?
Document Information
Modified date:
30 July 2021
UID
ibm16477000