Description of problem: We have following failed oslo-config-validation reported by couple of cu's. I think this needs to be updated since we see this is being set as default. ~~~ "action": "assert", "changed": false, "failed": true, "msg": "All items completed", "results": [ { "_ansible_item_label": "/var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf/cinder", "_ansible_no_log": false, "_ansible_verbose_always": true, "ansible_loop_var": "service", "assertion": "not service.output | count", "changed": false, "evaluated_to": false, "failed": true, "msg": "Config file /var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf for cinder has returned validation errors:\n ERROR:root:key_manager/backend is not part of the sample config\n", "service": { "config_file": "/var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf", "namespaces": [ "cinder", "keystonemiddleware.auth_token", "oslo.log", "oslo.messaging", "oslo.policy", "oslo.privsep", "oslo.service.periodic_task", "oslo.service.service", "oslo.db", "oslo.db.concurrency", "oslo.middleware", "oslo.concurrency", "osprofiler" ], "output": [ "ERROR:root:key_manager/backend is not part of the sample config" ], "service": "cinder" ~~~ Version-Release number of selected component (if applicable): 16.2.3 How reproducible: Steps to Reproduce: 1. Run validation post ffu 2. failure reported for oslo-config validation. 3. Actual results: failed validation Expected results: should pass Additional info:
I wasn't familiar with the validation framework until now, but I believe I see the problem and will post a patch. But I'm not sure why the problem was detected only after performing an FFU.
Patch has merged on stable/train, and should be available downstream on the next import.
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 (Release of components for Red Hat OpenStack Platform 16.2.4), 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-2022:8794