Docker 1.11.0 is unable to activate kuryr when docker plugin spec uses json

Bug #1572369 reported by Frederick F. Kautz IV
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr
Fix Released
Undecided
Unassigned

Bug Description

A full writeup is here:

https://github.com/docker/docker/issues/22175

In short, we can work around this by replacing the .json spec file with a .spec file.

Revision history for this message
Antoni Segura Puimedon (celebdor) wrote :

Docker 1.11.1 fixes it, but we'll take https://review.openstack.org/#/c/309104/ once comments are addressed.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr (master)

Reviewed: https://review.openstack.org/309104
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=07dca2a49ba1d127e1ca67463783e1f92346e1af
Submitter: Jenkins
Branch: master

commit 07dca2a49ba1d127e1ca67463783e1f92346e1af
Author: Frederick F. Kautz IV <email address hidden>
Date: Thu Apr 21 18:15:56 2016 -0700

    Activate libnetwork plugin with .spec instead of .json

    Docker 1.11.0 fails to activate libnetwork plugins specified with .json files.
    Using .spec files still works. Adding a .spec file and configuring devstack to
    work around the bug.

    Change-Id: I041a5e9a526c2e63c92f3d01411afda8b7beb601
    Closes-Bug: #1572369
    Signed-off-by: Frederick F. Kautz IV <email address hidden>

Changed in kuryr:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.