Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1575682 - Kuryr CNI Docker container needs to include CNI plugins binaries
Summary: Kuryr CNI Docker container needs to include CNI plugins binaries
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-kuryr-kubernetes
Version: 13.0 (Queens)
Hardware: All
OS: Linux
Target Milestone: beta
: 13.0 (Queens)
Assignee: Michał Dulko
QA Contact: GenadiC
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-07 15:34 UTC by Michał Dulko
Modified: 2018-05-09 14:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-09 14:18:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Michał Dulko 2018-05-07 15:34:34 UTC
Description of problem:
openshift-ansible now requires CNI plugins to insert CNI plugin binaries not through task in the playbook but through CNI container. This means that kuryr-cni container needs to include those binaries.

Version-Release number of selected component (if applicable):
0.4.3, but it only requires Dockerfile update, not the RPM update.

How reproducible:

Steps to Reproduce:
1. Use current Kuryr containers in openshift-ansible master installation
2. When installation finishes, deploy a new pod (e.g. oc run --image kuryr/demo)

Actual results:
Pod will never be created and openshift-node it is scheduled to will complain about loopback plugin missing.

Expected results:
Pod gets created without issues.

Additional info:
This only affects the Docker image, Kuryr-Kubernetes RPMs are fine and does not need an update.

Comment 2 Tomas Sedovic 2018-05-09 14:18:03 UTC
Closing this in favour of: https://bugzilla.redhat.com/show_bug.cgi?id=1571588

This issue is going to be fixed on the openshift-ansible side and the bug above has the right Product and Component set as well as tracking the upstream fix.

Note You need to log in before you can comment on or make changes to this bug.