Trove not working when OpenStack uses "insecure" SSL certificates
Bug #1535895 reported by
Vincent Untz
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Low
|
Tomasz |
Bug Description
If any of keystone, nova, cinder, heat, swift (any OpenStack component trove connects to) is using SSL but with certificates that cannot be verified (aka "insecure" certificates), then trove doesn't work.
There's no option to specify this in trove.conf.
I also quickly checked the code, and when we create the clients, we never pass the insecure flag.
Changed in trove: | |
milestone: | none → next |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in trove: | |
assignee: | Amrith Kumar (amrith) → Thomas Bechtold (toabctl) |
Changed in trove: | |
assignee: | Thomas Bechtold (toabctl) → Tomasz (nowak2000) |
To post a comment you must log in.
Vincent, I've assigned to myself as the bug is unassigned. I've looked at this area recently and am happy to fix.