Bug 1657276

Summary: [OSP10] fixed_key value is logged in the nova logs
Product: Red Hat OpenStack Reporter: Lee Yarwood <lyarwood>
Component: openstack-novaAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: dasmith, dhill, eglynn, jhakimra, kchamart, lyarwood, nova-maint, sbauza, sgordon, vromanso
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: openstack-nova-14.1.0-39.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1657275 Environment:
Last Closed: 2019-04-30 16:59:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1655740, 1657275    
Bug Blocks:    

Description Lee Yarwood 2018-12-07 14:57:05 UTC 
+++ This bug was initially created as a clone of Bug #1657275 +++

+++ This bug was initially created as a clone of Bug #1655740 +++

Description of problem:
fixed_key value is logged in the nova logs

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Set fixed_key value
2.
3.

Actual results:
It's logged in the logs

Expected results:
It shouldn't be logged

Additional info:

--- Additional comment from Lee Yarwood on 2018-12-06 12:31:32 EST ---

Lowering this to medium/medium as fixed_key isn't supported in production environments. The fact that we log the key during start up is the least of the issues with using it but never the less it should be removed. I'll pull this down into OSP 10 once it starts to land upstream.
Comment 10 errata-xmlrpc 2019-04-30 16:59:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0923