Openshift-ansible: No package matching 'origin-docker-excluder'

[DarkBlaez]

OS: Centos 7
Ansible: 2.4.0

I set up 2 masters, 2 etcd, 1 lb, 4 nodes. Playbook stops with:
No package matching 'origin-docker-excluder' found available, installed or updated across all masters and all nodes.

I saw other issues similar and thought this fix was checked in. However, this persist on current git pull

What is the resolution?

Thanks
DB

[wicksy]

+1

Dropped back to release openshift-ansible-3.5.28-1 to get things working as tried a couple of other recent releases but still failed.

OS: Centos 7.3.1611
Ansible: 2.2.0.0
openshift/openshift-ansible: Release openshift-ansible-3.6.4-1

[glenfordwilliams]

im also having this issue

[sdodson]

You should be able to work around this by setting enable_excluders=false in your inventory. This is happening due to a bug in the excluder packages themselves where origin-excluder excludes origin-docker-excluder so as soon as that package is installed the other is excluded from yum.

I guess the proper way forward is for us to disable this functionality unless they're running Origin 1.5 GA (yet to be released) which has the fix for this.

[DarkBlaez]

Using current 3.6 release and/or including current git pull, putting enable_excluders=false in the inventory yields another error

[OSEv3:vars]
ansible_ssh_user=root
deployment_type=origin
openshift_release=v1.4
osn_storage_plugin_deps=['glusterfs']
openshift_node_kubelet_args={'max-pods': ['40'], 'image-gc-high-threshold': ['90'], 'image-gc-low-threshold': ['80']}
enable_excluders=false

[...]

Error reported across the 2 masters and 4 nodes:

TASK [openshift_excluder : Enable docker excluder] ********************
fatal: [master01.somehost.etc]: FAILED! => {
"changed": false,
"cmd": "origin-docker-excluder exclude",
"failed": true,
"rc": 2
}

MSG:

[Errno 2] No such file or directory

Am I doing something wrong here? I assumed setting this in the VARS section would address this?

Thanks
DB

[DarkBlaez]

By adding enable_docker_excluder=false instead of adding enable_excluders=false allowed the playbook to run and complete without errors. Not sure why the first method did not work and what the impact will be. I assume this will be all fixed per prior mention once Origin 1.5GA is release

[sdodson]

Master should be fixed now as far as only needing enable_excluders=false I'll work on disabling this by default in origin today until centos paas sig repo has fixed excluder packages.

[jfillman]

I'm running into the same issue while trying to build origin in AWS. Sorry for my ignorance as i'm just getting familiar with ansible but WRT to the inventory config in the openshift-ansible-contrib git repo, where exactly do i add the 'enable-excluders=false' directive?

I don't see a typical inventory file with an [OSEv3:vars] section.

[kevinnchiu]

For openshift-ansible-contrib, can add enable_excluders=false to the ansible-playbook command extra-vars list to apply the workaround

[openshift-bot]

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-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.