Legacy nova/cinder key manager not specified when it needs to be
Bug #1706389 reported by
Alan Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Alan Bishop |
Bug Description
TripleO configures the proper Cinder/Nova key manager for Barbican deployments, but no key manager is
specified when Barbican isn't deployed. However, Cinder's and Nova's key manager no longer defaults to their legacy (fixed key) implementations [0],[1].
In order for non-Barbican deployments to work, TripleO must proactively enable the legacy key managers in Cinder and Nova.
[0] https:/
[1] https:/
Changed in tripleo: | |
assignee: | nobody → Alan Bishop (alan-bishop) |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → pike-rc1 |
importance: | Medium → High |
Changed in tripleo: | |
status: | Triaged → In Progress |
tags: | added: upgrade |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/488509
Review: https:/