MAS DevOps Ansible Collection Ansible CLI
Edit on GitHub
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

suite_rollback¤

This role is to roll back Maximo Application Suite to an earlier version. Rollback is possible only in 8.11 and later. From 8.11 onwards, every version comes with a set of supported versions to which Suite can be rolled back. For example, you can roll back Maximo Application Suite from 8.11.x to 8.11.0. This role validates given MAS installation is ready for the core platform to be rolled back to a specific MAS core version, and (as long as dry run mode is not enabled) will execute the rollback.

Role Variables¤

mas_instance_id¤

The ID of the MAS instance to rollback.

rollback_mas_core¤

When set to true will ensure that the role performs rollback operation.

verify_core_version¤

When set to true will ensure that the role checks the current MAS core version matches with specified version.

mas_core_version¤

The version of the MAS core that you want to rollback to or to validate current version. It is required when any of the ROLLBACK_MAS_CORE and VERIFY_CORE_VERSION variables is set to true.

mas_rollback_dryrun¤

When set to true will ensure that the role only preforms rollback validation checks and does not make any changes to the target installation.

Example Playbook¤

Automatic Target Selection¤

Running this playbook will rollback MAS core to the specified version. If you run this playbook when you are already on the same version it will take no action.

- hosts: localhost
  any_errors_fatal: true
  vars:
    mas_instance_id: instance1
    mas_core_version: 8.11.0
    mas_rollback_dryrun: False
  roles:
    - ibm.mas_devops.suite_rollback

Verify MAS core version¤

Running this playbook will attempt to verify the current version of MAS core matches with the specified version.

- hosts: localhost
  any_errors_fatal: true
  vars:
    mas_instance_id: instance1
    mas_core_version: 8.11.0
    mas_upgrade_dryrun: False
    rollback_mas_core: False
    verify_core_version: True
  roles:
    - ibm.mas_devops.suite_rollback