Trouble accessing generated DSA keys using CLI

Bug #1749882 reported by Kaitlin Farr
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-barbicanclient
In Progress
Undecided
Rajat Sharma

Bug Description

Steps to reproduce:

1. Generate a DSA key:
    openstack secret order create --bit-length 1024 --algorithm DSA --name "DSA key" asymmetric

2. Using the order href from the output from step 1, get the order details:
    openstack secret order get http://<order ref here>

3. Using the container href from the output from step 2, attempt to get the container details:
    openstack secret container get http://<container ref here>

Expected Result:
    the container details

Actual Result:
    "Unknown container type "dsa"."

It seems that barbican must create a container of type "dsa", which is not in barbicanclient's container_map. See https://github.com/openstack/python-barbicanclient/blob/49505b9aec05ec42e0a809ec51935c2324d5f3a6/barbicanclient/v1/containers.py#L521-L525

Rajat Sharma (tajar29)
Changed in python-barbicanclient:
status: New → Confirmed
Rajat Sharma (tajar29)
Changed in python-barbicanclient:
assignee: nobody → Rajat Sharma (tajar29)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-barbicanclient (master)

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

Changed in python-barbicanclient:
status: Confirmed → In Progress
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.