I'm trying to install the AI Service using [ibmmas/cli:21.2.0]mascli$ mas aiservice-install
I've made some previous attempts to install it with MAS Manage and also had problems, so I installed MAS Manage first and now I'm trying to install the AI Service on the same cluster.
I filled in the data correctly and when starting the pipeline during the pre-check, I get stuck on the following section (as per the log):
step-ocp-verify
Export all env vars defined in /workspace/settings
Using /opt/app-root/src/ansible.cfg as config file
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'
running playbook inside collection ibm.mas_devops
PLAY [localhost] ***************************************************************
TASK [Gathering Facts] ***********************************************
ok: [localhost]
TASK [ibm.mas_devops.ansible_version_check : Verify minimum Ansible version is 2.20.0] ***
ok: [localhost] => {
"changed": false,
"msg": "All assertions passed"
}
TASK [ibm.mas_devops.ansible_version_check : Check if mas-devops package is installed and meets minimum version] ***
ok: [localhost] => {"changed": false, "cmd": ["pip", "show", "mas-devops"], "delta": "0:00:00.314712", "end": "2026-05-15 17:01:40.589828", "failed_when_result": false, "msg": "", "rc": 0, "start": "2026-05-15 17:01:40.275116", "stderr": "", "stderr_lines": [], "stdout": "Name: mas-devops\nVersion: 9.16.1\nSummary: Python for Maximo Application Suite Dev/Ops\nHome-page: https://github.com/ibm-mas/python-devops\nAuthor: David Parker\nAuthor-email: parkerda@uk.ibm.com\nLicense: Eclipse Public License - v1.0\nLocation: /opt/app-root/lib64/python3.12/site-packages\nRequires: boto3, jinja2, jinja2-base64-filters, kubeconfig, kubernetes, openshift, packaging, pyyaml, semver, slack_sdk\nRequired-by: mas-cli", "stdout_lines": ["Name: mas-devops", "Version: 9.16.1", "Summary: Python for Maximo Application Suite Dev/Ops", "Home-page: https://github.com/ibm-mas/python-devops", "Author: David Parker", "Author-email: parkerda@uk.ibm.com", "License: Eclipse Public License - v1.0", "Location: /opt/app-root/lib64/python3.12/site-packages", "Requires: boto3, jinja2, jinja2-base64-filters, kubeconfig, kubernetes, openshift, packaging, pyyaml, semver, slack_sdk", "Required-by: mas-cli"]}
TASK [ibm.mas_devops.ansible_version_check : Get installed version of mas-devops] ***
ok: [localhost] => {"ansible_facts": {"mas_devops_version": ["9.16.1"]}, "changed": false}
TASK [ibm.mas_devops.ansible_version_check : Verify minimum mas-devops is installed] ***
ok: [localhost] => {
"changed": false,
"msg": "All assertions passed"
}
TASK [ibm.mas_devops.ansible_version_check : Verify minimum mas-devops version is 7.1.0] ***
ok: [localhost] => {
"changed": false,
"msg": "All assertions passed"
}
[WARNING]: Deprecation warnings can be disabled by setting `deprecation_warnings=False` in ansible.cfg.
[DEPRECATION WARNING]: Importing 'to_bytes' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.
[DEPRECATION WARNING]: Importing 'to_native' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.
[DEPRECATION WARNING]: Importing 'to_text' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.
TASK [ibm.mas_devops.ocp_verify : Check if cluster is ready] *******************
FAILED - RETRYING: [localhost]: Check if cluster is ready (60 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (59 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (58 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (57 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (56 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (55 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (54 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (53 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (52 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (51 retries left).
FAILED - RETRYING: [localhost]: Check if cluster is ready (50 retries left).
I also saw that during the creation of the pod affinity-assistant-01202606ef-0, the following warning was displayed in the event, preventing the pod from initializing:
Warning FailedScheduling 3m54s default-scheduler 0/2 nodes are available: persistentvolumeclaim "config-pvc" not found. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
I manually created the PVC to see if it would fix the pod, and it did.
However, the precheck remained stuck, and the following event appeared: testeai-install-260515-1701-pre-install-check
NamespaceNSaiservice-testeai-pipelines
15/05/2026, 14:01
Generated from taskrun-controller
2 times in the last 35 minutes
Failed to update finalizers for "testeai-install-260515-1701-pre-install-check": Operation cannot be fulfilled on taskruns.tekton.dev "testeai-install-260515-1701-pre-install-check": the object has been modified; please apply your changes to the latest version and try again
Coul you help us?
I'm trying to install the AI Service using [ibmmas/cli:21.2.0]mascli$ mas aiservice-install
I've made some previous attempts to install it with MAS Manage and also had problems, so I installed MAS Manage first and now I'm trying to install the AI Service on the same cluster.
I filled in the data correctly and when starting the pipeline during the pre-check, I get stuck on the following section (as per the log):
I also saw that during the creation of the pod affinity-assistant-01202606ef-0, the following warning was displayed in the event, preventing the pod from initializing:
Warning FailedScheduling 3m54s default-scheduler 0/2 nodes are available: persistentvolumeclaim "config-pvc" not found. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
I manually created the PVC to see if it would fix the pod, and it did.
However, the precheck remained stuck, and the following event appeared: testeai-install-260515-1701-pre-install-check
NamespaceNSaiservice-testeai-pipelines
15/05/2026, 14:01
Generated from taskrun-controller
2 times in the last 35 minutes
Failed to update finalizers for "testeai-install-260515-1701-pre-install-check": Operation cannot be fulfilled on taskruns.tekton.dev "testeai-install-260515-1701-pre-install-check": the object has been modified; please apply your changes to the latest version and try again
Coul you help us?