Maximo Open Forum

 View Only

 Error encountered during MAS Manage installation using ansible script

Jump to  Best Answer
  • Everything Maximo
Vincent Yap's profile image
Vincent Yap posted 12-07-2024 12:14

Hi Experts,

We ran into an error below during installation of MAS Manage using ansible script playbook

Error text captured below:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible_collections.kubernetes.core.plugins.module_utils.k8s.exceptions.CoreException: Failed to gather information about ManageWorkspace(s) even after waiting for 120 seconds
fatal: [localhost]: FAILED! => {"attempts": 60, "changed": false, "msg": "Failed to gather information about ManageWorkspace(s) even after waiting for 120 seconds"}

Ansible scripts used:

export MAS_APP_ID=manage
export MAS_ANNOTATIONS=mas.ibm.com/operationalMode=nonproduction
export MAS_CONFIG_DIR=~/masconfig
export MAS_WORKSPACE_ID=mas9qa
export MAS_WORKSPACE_NAME=mas9qa
export MAS_INSTANCE_ID=mas9qa
export DB2_DBNAME=BLUDB
export DB2_INSTANCE_NAME=mas9qa
export MAS_APPWS_COMPONENTS="base=latest"
export ENFORCE_DB2_CONFIG=True
export DB2_ENTITLEMENT_KEY=xxx
export MAS_ENTITLEMENT_KEY=xxx
export IBM_ENTITLEMENT_KEY=xxx
export DB2_META_STORAGE_ACCESSMODE=ReadWriteOnce
export DB2_META_STORAGE_SIZE=20Gi
export DB2_META_STORAGE_CLASS=gp3-csi
export DB2_DATA_STORAGE_ACCESSMODE=ReadWriteOnce
export DB2_DATA_STORAGE_SIZE=100Gi
export DB2_DATA_STORAGE_CLASS=gp3-csi
export DB2_BACKUP_STORAGE_ACCESSMODE=ReadWriteOnce
export DB2_BACKUP_STORAGE_SIZE=100Gi
export DB2_BACKUP_STORAGE_CLASS=gp3-csi
export DB2_CPU_REQUESTS=4000m
export DB2_CPU_LIMITS=6000m
export DB2_MEMORY_REQUESTS=32Gi
export DB2_MEMORY_LIMITS=64Gi
export DB2_LOGS_STORAGE_ACCESSMODE=ReadWriteOnce
export DB2_LOGS_STORAGE_CLASS=gp3-csi
export DB2_LOGS_STORAGE_SIZE=100Gi
export DB2_TEMP_STORAGE_ACCESSMODE=ReadWriteOnce
export DB2_TEMP_STORAGE_SIZE=100Gi
export DB2_TEMP_STORAGE_CLASS=gp3-csi
export KUBECONFIG=/home/ec2-user/openshift/installer/auth/kubeconfig
export MAS_APP_UPGRADE_STRATEGY=Manual

oc login --token=xxx --server=xxx

ansible-playbook ibm.mas_devops.oneclick_add_manage

Per checking the MAS manage workspace an error is shown below:

Please advise on error encountered or if missed something from script above

Thanks

Vincent Yap's profile image
Vincent Yap  Best Answer

Issue was resolved by using correct workspace. Checked the masconfig folder in Bastion host to see correct workspace name.