trove service cannot be configured to talk to https endpoints for other openstack services

Bug #1421758 reported by Saurabh Surana on 2015-02-13
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
High
Unassigned

Bug Description

If https is enabled for nova/keystone/cinder/swift, trove services are not able to talk to such endpoints as we don't pass the ca_certificate parameter to various clients we create in remote.py

Changed in trove:
assignee: nobody → Saurabh Surana (saurabh-surana)
Craig Vyvial (cp16net) on 2016-02-08
Changed in trove:
assignee: Saurabh Surana (saurabh-surana) → nobody
Amrith Kumar (amrith) wrote :

I'm fixing this.

Changed in trove:
assignee: nobody → Amrith (amrith)
Amrith Kumar (amrith) on 2016-04-05
Changed in trove:
status: New → Confirmed
milestone: none → newton-1
importance: Undecided → High
Amrith Kumar (amrith) on 2016-09-18
Changed in trove:
milestone: newton-1 → ongoing
Amrith Kumar (amrith) on 2017-09-28
Changed in trove:
assignee: Amrith Kumar (amrith) → nobody
Krzysztof Opasiak (kopasiak) wrote :

Is this bug still valid or it has been already fixed?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers