Description of problem: Install OpenShift on Atomic Host with RHEL as NFS server without OCP repo as before, Installation failed. Version-Release number of selected component (if applicable): openshift-ansible-3.6.94-1.git.0.fff177b.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1. Install OpenShift on Atomic Host with RHEL as NFS server without OCP repo [masters] AH host1 [nodes] AH host1 AH host2 [nfs] RHEL host1 Actual results: Installation FAILURE Failure summary: 1. Host: RHEL host1 Play: Verify Requirements Task: openshift_version : fail Message: Package atomic-openshift not found Expected results: Installation SUCCESS as before Additional info:
Doing a little debugging the issue stems from this pattern: 1. openshift_version is a dependency of openshift_health_checker 2. openshift_version includes set_version_rpm.yml as is_containerized is False 3. roles/openshift_version/tasks/set_version_rpm.yml uses repoquery to find atomic-openshift, but it is not there in this scenario.
PR: https://github.com/openshift/openshift-ansible/pull/4495
This is fail task in the openshift_version role. It's just reported under the same summary as checks would be (all failures are now). So excluding the NFS host from checks won't actually address this (although it might be necessary to do that too).
I follow what you're saying Luke. It looks like there are three locations which include the role: roles/openshift_health_checker/meta/main.yml: Noted here with scoped hosts roles/openshift_common/meta/main.yml: Includes without scoping hosts roles/openshift_docker/meta/main.yml: Includes without scoping hosts I'll look at trying to keep nfs and lbs out of package checking rather than skipping them within the health checks.
not fixed with openshift-ansible-3.6.126-1.git.0.58d33f0.el7.noarch.rpm
in openshift-ansible-3.6.123.1002-1.git.0.506cfa7.el7
I would like to wait for 3.6.127 to verify
Verified on openshift-ansible-3.6.123.1002-1.git.0.506cfa7.el7.noarch.rpm Fixed. Install SUCCESS
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/RHEA-2017:1716