Recent changes in Nova [0] and Cinder [1] result in Barbican being selected
as the default encryption key manager, even when TripleO is not deploying
Barbican.
This change ensures the legacy key manager is enabled when no key manager
(such as Barbican) has been specified. This restores the previous behavior,
where the legacy key manager was enabled by default.
Reviewed: https:/ /review. openstack. org/488509 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=5ae3fab7438 1403cc76525ba3f f63a60836c17c1
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5ae3fab74381403 cc76525ba3ff63a 60836c17c1
Author: Alan Bishop <email address hidden>
Date: Fri Jul 28 10:30:27 2017 -0400
Fix legacy nova/cinder encryption key manager configuration
Recent changes in Nova [0] and Cinder [1] result in Barbican being selected
as the default encryption key manager, even when TripleO is not deploying
Barbican.
This change ensures the legacy key manager is enabled when no key manager
(such as Barbican) has been specified. This restores the previous behavior,
where the legacy key manager was enabled by default.
[0] https:/ /review. openstack. org/484501 /review. openstack. org/485322
[1] https:/
Closes-Bug: #1706389 7538eaac51c4ad8 dc397f9c3d3
Change-Id: Idc92f7a77cde75