Calling barbican action complains about unknown insecure parameter

Bug #1800819 reported by Jose Castro Leon on 2018-10-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jose Castro Leon

Bug Description

While calling a barbican action, the _get_client_class tries to establish a connection with the barbican server. This method of initialize the server is quite different to other clients as it is using the token instead the session and also specifies an insecure parameter that does not exist in the client class.

Due to this all barbican actions fail to execute.

Changed in mistral:
assignee: nobody → Jose Castro Leon (jose-castro-leon)
Changed in mistral:
status: New → In Progress
Dougal Matthews (d0ugal) on 2018-11-30
Changed in mistral:
importance: Undecided → Medium
Changed in mistral:
milestone: none → train-1

Submitter: Zuul
Branch: master

commit eb592162817184b1d8b3c9b3e576ebc0715ec350
Author: Jose Castro Leon <email address hidden>
Date: Wed Oct 31 13:32:31 2018 +0100

    Removes insecure parameter from barbican client

    This removes the parameter insecure in the client creation as this
    no longer exists in the client. It also changes the client class
    to be called as other clients in openstack using sessions

    Change-Id: I3cb7ed4255f8996b8bfd9a3e1edba6de50f4e492
    Closes-Bug: #1800819

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

Other bug subscribers