vim configuration does not allow the INSECURE property

Bug #1719841 reported by Manuel Buil
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released
Cong Phuoc Hoang

Bug Description

There are openstack deployments which use self-signed certificates which require the variable OS_INSECURE to be 'true' in order to communicate with endpoints that use SSL. This is unfortunately not possible to configure in the vim config file when registering a vim. Therefore, tacker is does not work on openstack deployments that use self-signed certificates

Manuel Buil (mbuil)
Changed in tacker:
assignee: nobody → Manuel Buil (mbuil)
Changed in tacker:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-2
Changed in tacker:
milestone: pike-2 → queens-3
assignee: Manuel Buil (mbuil) → nobody
Taseer Ahmed (taseer94)
Changed in tacker:
assignee: nobody → Taseer Ahmed (taseer94)
Revision history for this message
yong sheng gong (gongysh) wrote :

Taseer Ahmed, do you have time for it?

Changed in tacker:
assignee: Taseer Ahmed (taseer94) → Cong Phuoc Hoang (hoangphuoc)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Submitter: Zuul
Branch: master

commit e1f3d8285cbf8a662605027e62fb23d4ff7e4a2f
Author: Manuel Buil <email address hidden>
Date: Wed Dec 20 18:02:33 2017 +0100

    Check if certificates must be verified in the vim

    This patch tries to fix the bug:

    To disable the verification, a parameter must be included in vim_config.yaml
    cert_verify: 'False'

    Co-Authored-By: Cong Phuoc Hoang <email address hidden>
    Closes-Bug: #1719841

    Change-Id: If9c8eab81bad2028ae146598d559831bc51cbbf5
    Signed-off-by: Manuel Buil <email address hidden>

Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 0.9.0

This issue was fixed in the openstack/tacker 0.9.0 release.

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.