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
Home Roles: OCP Mgmt ocp_verify Role Variables Example Playbook License

ocp_verify¤

This role will verify that the target OCP cluster is ready to be setup for MAS.

For example, in IBMCloud ROKS we have seen delays of over an hour before the Red Hat Operator catalog is ready to use. This will cause attempts to install anything from that CatalogSource to fail as the timeouts built into the roles in this collection are designed to catch problems with an install, rather than a half-provisioned cluster that is not properly ready to use yet.

Role Variables¤

verify_cluster¤

Enables verification that the cluster is healthy and ready to use. This check runs against the ClusterVersion resource and expects the Ready condition to be set to true. If the cluster is not ready within 1 hour the verification will fail.

verify_catalogsources¤

Enables verification that all installed catalog sources are healthy. If any CatalogSources are not reporting lastObservedState as READY after 30 minutes then the verification will fail.

verify_subscriptions¤

Enables verification that all operator subscriptions are up to date. If any Subscriptions are not reporting state as AtLatestKnown after 5 hours then the verification will fail.

verify_workloads¤

Enables verification that all operator subscriptions are up to date. If any Deployments or StatefulSets are not reporting updatedReplicas & availableReplicas equal to replicasafter 10 hours then the verification will fail.

verify_ingress¤

Enables verification that the cluster ingress TLS certificate can be ontained. This is required by a number of roles in the collection.

cluster_name¤

Specify the name of the cluster, in some cluster setups this name is required to determine the name of the default router certificate.

ocp_ingress_tls_secret_name¤

Specify the name of the cluster's ingres tls secret which contains the default router certificate.

Example Playbook¤

- hosts: localhost
  vars:
    verify_cluster: True
    verify_catalogsources: True
    verify_subscriptions: True
    verify_workloads: True
    verify_ingress: True
  roles:
    - ibm.mas_devops.ocp_verify

License¤

EPL-2.0