Description of problem: Fail to container install ocp with specified openshift_additional_repos in inventory file due to no excluder packages found. This is because the installer didn't configure openshift_additional_repo on the RHEL hosts prior to installing `atomic-openshift-docker-excluder`. fatal: [openshift-151.x.x.x]: FAILED! => { "changed": false, "failed": true, "invocation": { "module_args": { "conf_file": null, "disable_gpg_check": false, "disablerepo": null, "enablerepo": null, "exclude": null, "install_repoquery": true, "list": null, "name": [ "atomic-openshift-docker-excluder-3.4.1.44*" ], "state": "present", "update_cache": false, "validate_certs": true } }, "rc": 126, "results": [ "No package matching 'atomic-openshift-docker-excluder-3.4.1.44*' found available, installed or updated" ] } MSG: No package matching 'atomic-openshift-docker-excluder-3.4.1.44*' found available, installed or updated Version-Release number of selected component (if applicable): atomic-openshift-utils-3.4.111-1.git.0.61ef2e0.el7.noarch How reproducible: always Steps to Reproduce: 1. Edit inventory file to add openshift_additional_repos="xxxx" 2. Trigger container install on the host without ose3.6 repo 3. Actual results: openshift_addtional_repo not configured on the RHEL hosts, then install failed with no corresponding `atomic-openshift-docker-excluder` found. Expected results: Install succeed with both of excluders installed. Additional info:
Liujia, can you run just 'yum install atomic-openshift-docker-excluder' on the openshift-151.x.x.x host? To see if any version of the excluder is available?
(In reply to Jan Chaloupka from comment #1) > Liujia, can you run just 'yum install atomic-openshift-docker-excluder' on > the openshift-151.x.x.x host? To see if any version of the excluder is > available? Jan, no any version of the excluder would be available. Because there are no ose3.4 repo was created on the host, which should be generated by installer through setting openshift_additional_repo="". BTW, this issue only happened on 3.3/3.4 version, it works well on 3.5/3.6.
This problem won't affect production environments because repos are configured during pre-requisites so closed wontfix.