Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openshift_excluder: No package matching 'origin-excluder*' #13516

Closed
jovemfelix opened this issue Mar 22, 2017 · 8 comments
Closed

openshift_excluder: No package matching 'origin-excluder*' #13516

jovemfelix opened this issue Mar 22, 2017 · 8 comments
Assignees
Labels
component/install kind/question lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2

Comments

@jovemfelix
Copy link

jovemfelix commented Mar 22, 2017

[ansible TASK [openshift_excluder : Install openshift excluder] not working]

Version

Trying to install the master, using ansible 2.4.0, at RHEL Server release 7.3 (Maipo)

Steps To Reproduce
  1. Configure /etc/ansible/hosts using this configuration example "Example 1. Single Master and Multiple Nodes Inventory File" explained in https://access.redhat.com/documentation/en-us/openshift_container_platform/3.4/html-single/installation_and_configuration/
  2. change directory to xxxx/openshift-ansible/playbooks/byo
  3. run command line: ansible-playbook config.yml -k -c paramiko
Current Result
TASK [openshift_excluder : Install openshift excluder] *************************************************************
fatal: [openshift2.lab.fnde.gov.br]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'origin-excluder*' found available, installed or updated", "rc": 126, "results": ["No package matching 'origin-excluder*' found available, installed or updated"]}
fatal: [openshift3.lab.fnde.gov.br]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'origin-excluder*' found available, installed or updated", "rc": 126, "results": ["No package matching 'origin-excluder*' found available, installed or updated"]}
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'origin-excluder*' found available, installed or updated", "rc": 126, "results": ["No package matching 'origin-excluder*' found available, installed or updated"]}
	to retry, use: --limit @/root/openshift-ansible/playbooks/byo/config.retry

PLAY RECAP 
*************************************************************
localhost                  : ok=49   changed=0    unreachable=0    failed=1
openshift2.lab.fnde.gov.br : ok=39   changed=0    unreachable=0    failed=1
openshift3.lab.fnde.gov.br : ok=39   changed=0    unreachable=0    failed=1
Expected Result

Next step of installation.

@stevekuznetsov
Copy link
Contributor

There may be a mis-match between the version of the openshift-ansible installer you are using and the version of OpenShift you want to install -- can you provide us with:

$ rpm -q openshift-ansible
$ yum list available origin*

What repositories are you using to install openshift-ansible and/or origin?

@jovemfelix
Copy link
Author

Sorry for the late answer...

after run rpm -q openshift-ansible a got
package openshift-ansible is not installed

after frun yum list available origin* a got
Loaded plugins: product-id, rhnplugin, search-disabled-repos, subscription-manager This system is receiving updates from RHN Classic or Red Hat Satellite. Error: No matching Packages to list

So I could by pass it removing exclude parameter into /etc/yum.conf of each master and node machine
#exclude=origin-docker-excluder ....

Thanks!

@stevekuznetsov
Copy link
Contributor

@sdodson was the excluder on by default for 3.4?

@jovemfelix
Copy link
Author

jovemfelix commented Mar 29, 2017 via email

@sdodson
Copy link
Member

sdodson commented Mar 29, 2017

@sdodson was the excluder on by default for 3.4?

Only if you've used the master or release-1.5 branch to install 3.4.

@stevekuznetsov
Copy link
Contributor

@jovemfelix so to get the output with the excluder installed (which it seems is your case), use:

yum --disableexcludes=all list installed openshift-ansible*
yum --disableexcludes=all list installed atomic-openshift*
yum --disableexcludes=all list installed origin*

Alternatively, if you did not install the openshift-ansible playbooks through yum, what version did you use to install? You've linked installation documents for OpenShift Container Platform 3.4, for which the excluder was not installed by default, so perhaps this is a misconfigured installation inventory. We'll need more information about the version of the installer you're using, version of OpenShift you meant to install, extra parameters you added to the inventory, etc.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2018
@stevekuznetsov
Copy link
Contributor

Without more information, cannot aid any more.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/install kind/question lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2
Projects
None yet
Development

No branches or pull requests

6 participants