Maximo Predict Installation failure during SUITE-APP-CONFIG

[rene-oromtz]

Summary

During Predict installation via mas install, the Predict app configuration fails as it timeout.
MAS installation was deployed from scratch and all others steps succeeded (MongoDB, DB2, CP4D Services and Maximo apps/tools):

From the predict-entitymgr-ws pod, the following error is presented:

TASK [Check Integration Status] ********************************
fatal: [localhost]: FAILED! => {"APP UP RUNNING SINCE (UTC)": "2024/03/07 07:59:59", "CURRENT SERVER TIME (UTC)": "2024/03/07 15:07:18", "DB": "CONNECTED", "MAS_INT_STATUS": "PENDING", "PREDICT": "ALIVE", "SPSS": "The url is internal url. Please set url to be external url.", "SSL": "TRUE", "WATSON_MACINE_LEARNING": "The url is internal url. Please set url to be external url.", "WATSON_STUDIO": "The url is internal url. Please set url to be external url.", "attempts": 30, "changed": false}
-------------------------------------------------------------------------------
{"level":"error","ts":"2024-03-07T15:07:18Z","logger":"logging_event_handler","msg":"","name":"arft-masdev","namespace":"mas-arft-predict","gvk":"apps.mas.ibm.com/v1, Kind=PredictWorkspace","event_type":"runner_on_failed","job":"8572090521397372376","EventData.Task":"Check Integration Status","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/roles/predictworkspace/tasks/checkPredictStatus.yml:2","error":"[playbook task failed]","stacktrace":"github.com/operator-framework/ansible-operator-plugins/internal/ansible/events.loggingEventHandler.Handle\n\tansible-operator-plugins/internal/ansible/events/log_events.go:111"}
{"level":"error","ts":"2024-03-07T15:07:18Z","logger":"runner","msg":"\u001b[0;34mansible-playbook [core 2.15.3]\u001b[0m\r\n\u001b[0;34m config file = /etc/ansible/ansible.cfg\u001b[0m\r\n\u001b[0;34m configured module search path = ['/opt/ansible/library']\u001b[0m\r\n\u001b[0;34m ansible python module location = /usr/local/lib/python3.9/site-packages/ansible\u001b[0m\r\n\u001b[0;34m ansible collection location = /opt/ansible/.ansible/collections:/usr/share/ansible/collections\u001b[0m\r\n\u001b[0;34m executable location = /usr/local/bin/ansible-playbook\u001b[0m\r\n\u001b[0;34m python version = 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] (/usr/bin/python3)\u001b[0m\r\n\u001b[0;34m jinja version = 3.1.2\u001b[0m\r\n\u001b[0;34m libyaml = True\u001b[0m\r\n\u001b[0;34mUsing /etc/ansible/ansible.cfg as config file\u001b[0m\r\n\u001b[0;34mSkipping callback 'awx_display', as we already have a stdout callback.\u001b[0m\n\u001b[0;34mSkipping callback 'default', as we alr...
----- Ansible Task Status Event StdOut (apps.mas.ibm.com/v1, Kind=PredictWorkspace, arft-masdev/mas-arft-predict) -----
PLAY RECAP *********************************************************************
localhost : ok=323 changed=12 unreachable=0 failed=1 skipped=95 rescued=0 ignored=0

From WS/WML, the following reference is of interest:
The url is internal url. Please set url to be external url

As per Maximo suite config app reference, the default url is set to:
https://internal-nginx-svc.ibm-cpd.svc:12443

Steps to reproduce:

1. Install all Maximo prerequisites for Predict app by using mas install
2. Wait for all services/apps to be installed and configured
3. During Maximo Predict Activation, access to predict-entitymgr-ws to see the previously mentioned error:

What is the current bug behavior?

predict is selecting default url https://internal-nginx-svc.ibm-cpd.svc:12443, however, this is not the cp4d url that was configured during installation. Not sure if this url is valid for any case or it will always need to be changed.

What is the expected correct behavior?

One click installer / suite app config does include the option to add the variable CPD_WML_URL, however, during mas install, this setting is not being prompted to be set.

Possible fixes

One possible enhancement is that if mas install is going to install all cp4d services to automatically pick the cp4d URL that was installed.

Workaround

Had to access to Predict application and modify the url

After the URL was set with the CP4D URL, it took couple minutes to reconcile and complete activation for Maximo Predict