Troubleshooting
Problem
During the IBM Maximo Application Suite upgrade, the Coreidp entity manager operator identified by {instanceId}-entitymgr-coreidp (where instanceId is the ID you used to create your IBM Maximo Application Suite instance), might fail on the task to create the job for OIDC Client.
As an example, you will see the following errors in the coreidp entity manager operator's log:
TASK [Create Job for MAS OIDC client Registration] ********************************
[0;31mfatal: [localhost]: FAILED! => {"changed": false, "error": 422, "msg": "Failed to patch object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"Job.batch \\\\\"ivt5-oidcclientreg\\\\\" is invalid: spec.template: Invalid value: core.PodTemplateSpec{ObjectMeta:v1.ObjectMeta{Name:\\\\\"oidcclientreg\\\\\", GenerateName:\\\\\"\\\\\", Namespace:\\\\\"\\\\\", SelfLink:\\\\\"\\\\\", UID:\\\\\"\\\\\", ResourceVersion:\\\\\"\\\\\", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string{\\\\\"controller-uid\\\\\":\\\\\"71d9dcba-cc77-4729-a92b-40a263003191\\\\\", \\\\\"job-name\\\\\":\\\\\"ivt5-oidcclientreg\\\\\"}, ...
Symptom
One of the coreidp entity manager operator tasks is to create the routes and apply certificates against it, but when it hits this error, the certificates are not applied as the coreidp operator will get stuck into this failing task and never get to the point when it creates/updates the routes with the valid certificates. This is likely to become a problem, when the certificate rotation time period is reached and Maximo Application Suite automatically tries to renew the certificates.
Resolving The Problem
To solve the problem
1- First go to OpenShift Console.
2- Go to Workloads, then Jobs.
3- With the instanceId you provided to install your instance, search for `{instanceId}-oidcclientreg`.
4- In the Three dots menu beside the registry and select 'Delete Job'
Or if you click the Job, you can delete by going to 'Actions' drop-down menu and select 'Delete Job'
5- It will ask you if you want to delete its depends objects, click Delete to complete. It will delete both job and pod.
6 - Wait for Coreidp operator to reconcile, and the issue should not be seen anymore.
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":"a8m3p000000hAeeAAE","label":"Maximo Application Suite->Core"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
17 September 2021
UID
ibm16485761