when using IBM CLI to install MAS and include Cognos Analytics the cp4d pipeline fails.
Steps to reproduce]
1) Pull MAS CLI v7.15.0 or 7.15.1
3) Run interactive "mas install"
4) Conduct basic MAS+Manage install selections with Jan 30 2024 catalog, making sure to select yes to Cognos Analytics:
"Install Cognos Analytics [y/N] y"
STEP-CP4D
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.10.3] ***
ok: [localhost] => changed=false
msg: All assertions passed
TASK [ibm.mas_devops.cp4d : Check that CPD release version has been provided] ***
fatal: [localhost]: FAILED! => changed=false
assertion: cpd_product_version is defined and cpd_product_version != ""
evaluated_to: false
msg: CPD version (cpd_product_version) is a required parameter to run this role
NO MORE HOSTS LEFT *************************************************************
PLAY RECAP *********************************************************************
localhost : ok=2 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
Work around
Currently there's a limitation in CLI that only when Predict or Assist is installed it automatically sets the CP4D_VERSION value.
Customer can manually export this env var CP4D_VERSION=4.6.6 and run install.
I reproduce the issue but the work around doesn't work for me.
I tried export CP4D_VERSION=4.6.6 and also export CPD_PRODUCT_VERSION=4.6.6 but I still have the issue you mention when running install.
Problem description
when using IBM CLI to install MAS and include Cognos Analytics the cp4d pipeline fails.
Steps to reproduce]
1) Pull MAS CLI v7.15.0 or 7.15.1 3) Run interactive "mas install" 4) Conduct basic MAS+Manage install selections with Jan 30 2024 catalog, making sure to select yes to Cognos Analytics: "Install Cognos Analytics [y/N] y"
CLI details
Log extras
Work around
Currently there's a limitation in CLI that only when Predict or Assist is installed it automatically sets the CP4D_VERSION value. Customer can manually export this env var CP4D_VERSION=4.6.6 and run install.