MAS DevOps Ansible Collection Ansible CLI
Home Ansible Automation Platform OCP Install Cloud Pak For Data Install Core Add AIBroker Add IoT Add Manage Add Monitor Add Optimizer Add Predict Add Visual Inspection Update Upgrade Uninstall Core Backup & Restore ocp_cluster_monitoring ocp_config ocp_deprovision ocp_efs ocp_github_oauth ocp_login ocp_node_config ocp_provision ocp_roks_upgrade_registry_storage ocp_upgrade ocp_verify appconnect aws_bucket_access_point aws_documentdb_user aws_policy aws_route53 aws_user_creation aws_vpc cert_manager cis common-services configure_manage_eventstreams cos cos_bucket cp4d_admin_pwd_update cp4d cp4d_service db2 dro eck grafana ibm_catalogs kafka nvidia_gpu mongodb ocs sls turbonomic uds mirror_case_prepare mirror_extras_prepare mirror_images mirror_ocp ocp_idms ocp_simulate_disconnected_network registry suite_app_config suite_app_install suite_app_uninstall suite_app_upgrade suite_app_rollback suite_app_backup_restore suite_certs suite_config suite_db2_setup_for_manage suite_dns suite_install suite_manage_attachments_config suite_manage_birt_report_config suite_manage_bim_config suite_manage_customer_files_config suite_manage_imagestitching_config suite_manage_import_certs_config suite_manage_load_dbc_scripts suite_manage_logging_config suite_manage_pvc_config suite_uninstall suite_upgrade suite_rollback suite_verify suite_backup_restore ansible_version_check entitlement_key_rotation gencfg_jdbc gencfg_watsonstudio gencfg_workspace gencfg_mongo

Uninstall for MAS Core¤

This playbook will remove MAS Core Platform and its dependencies from your cluster. If you have installed any MAS applications you should uninstall them first. This playbook will effectively undo everything done in the oneclick-core playbook.

The following will be removed from the cluster. - MAS Core Platform for the specified instance ID - IBM Suite Licensing Service - MongoDb - IBM User Data Services - IBM Certificate Manager - IBM Cloud Pak Foundational Services - IBM Maximo Operator Catalog - Cluster Monitoring (including Grafana)

When using this playbook be sure that nothing else in your cluster is using any of the dependencies that will be removed. If you wish to skip the removal of one or more dependencies use the optional environment variables documented below to control exactly what is uninstalled.

Warning

This playbook will try to gracefully uninstall a target MAS instance by removing MAS related resources in the expected order. Therefore, make sure your MAS operator is up and running in a healthy state, and no errors are reported in your Suite custom resource.

If there are any error reported in the logs of your MAS operator pod, or in your Suite custom resource, the uninstall process might get stuck and not complete successfully. In this case, you will need to debug and fix what is preventing your MAS operator to properly process the uninstall, or ultimately, forcibly uninstall MAS instance.

For more information regarding MAS uninstall process, refer to Uninstalling Maximo Application Suite documentation.

Usage¤

Required environment variables¤

Optional environment variables¤

Any of these environment variables can be set to none to skip the uninstall of the associated dependency, this can be useful if you have multiple MAS instances installed on a single cluster for example.

Warning

Although you could set the actions to install and run the playbook it is strongly recommended not to as it runs through the dependencies in the reverse order that they need to be installed in; use the oneclick-core playbook to repair a MAS Core installation.

mas_wipe_mongo_data¤

Defines whether Mongo databases should be deleted along with MAS uninstall

Example¤

export MAS_INSTANCE_ID=inst1

oc login --token=xxxx --server=https://myocpserver
ansible-playbook ibm.mas_devops.uninstall_core

Tip

If you do not want to set up all the dependencies on your local system, you can run the install inside our docker image as well: docker run -ti --pull always quay.io/ibmmas/cli