400 error on getting certificates from Barbican

Bug #1506906 reported by hongbin
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
High
hongbin

Bug Description

Steps to reproduce:

1. Enable Barbican on devstack.
2. Ensure cert_manager_type is barbican in Magnum config file (/etc/magnum/magnum.conf)
3. Create a secure k8s bay:
4. Create a pod

Then, you should see the pod creation failed:

$ magnum pod-create --manifest ./redis-master.yaml --bay k8sbay
ERROR: Remote error: HTTPClientError Bad Request
[u' (HTTP 500)

Here is the log in magnum conductor:

http://paste.openstack.org/show/476502/

hongbin (hongbin034)
Changed in magnum:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/236094

Changed in magnum:
assignee: nobody → hongbin (hongbin034)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/236094
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=18b61bce5124120e1534a95c2afb3bc572cdc215
Submitter: Jenkins
Branch: master

commit 18b61bce5124120e1534a95c2afb3bc572cdc215
Author: Hongbin Lu <email address hidden>
Date: Fri Oct 16 16:49:08 2015 -0400

    Fix incorrect usage of CertManager in k8s_api

    This should fix a 400 error on getting certificates from Barbican.

    Change-Id: I5cd934ba0df41fe34e74ae7c90febeccc821f758
    Closes-Bug: #1506906

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-2
status: Fix Committed → Fix Released
Adrian Otto (aotto)
Changed in magnum:
milestone: mitaka-2 → mitaka-1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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