Red Hat Bugzilla – Bug 1483931
Verify_health_checks.yml is not in upgrade_nodes.yml and upgrade_control_plane.yml
Last modified: 2017-11-28 17:07:41 EST
Description of problem: The Disk and memory check is not in openshift-ansible/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_nodes.yml&upgrade_control_plane.yml Version-Release number of the following components: openshift-ansible: master How reproducible: always Steps to Reproduce: 1. Check code in openshift-ansible/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml 2. Check code in openshift-ansible/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_nodes.yml Actual results: verify_health_checks.yml is not in openshift-ansible/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_nodes.yml&upgrade_control_plane.yml Expected results: upgrade_nodes.yml&upgrade_control_plane.yml should include verify_health_checks.yml to enable disk/memory check feature Additional info:
Juan, could you help triage this please? Is it something that is intentionally missing or a bug?
From what I can tell, both the memory availability and disk space checks are included as part of the 3.7 upgrade path under the "verify_health_checks.yml" playbook: https://github.com/openshift/openshift-ansible/blob/master/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade.yml#L74
@Juan, there are three entry playbooks for upgrade - upgrade.yml, upgrade_control_plane.yml and upgrade_nodes.yml. verify_health_checks.yml also need to be added in [2] and [3]. For more detail, refer to [1] [1] https://docs.openshift.com/container-platform/3.6/install_config/upgrading/automated_upgrades.html#upgrading-control-plane-nodes-separate-phases [2]https://github.com/openshift/openshift-ansible/blob/master/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml [3]https://github.com/openshift/openshift-ansible/blob/master/playbooks/common/openshift-cluster/upgrades/v3_7/upgrade_nodes.yml
@anli thanks, opened PR to address this here: https://github.com/openshift/openshift-ansible/pull/5357
This is really more an enhancement than a bug; we will plan to merge it next week during the normal merge window.
Verified and pass on openshift-ansible-3.7.0-0.189.0.git.0.d497c5e.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188