Description of problem: Currently we don't have a way to configure cors in gnocchi.conf via tripleo installer. We should expose these in puppet-gnocchi and set them from tripleo to make it persistent. Otherwise if you manually change these config, they will get wiped after the container reboots.
Changing back as we don't have tripleo support yet.
Fixed in puppet-gnocchi-12.4.0-4.el7ost and puppet-tripleo-8.5.1-6.el7ost
Hu,Martin. Please,provide instructions for QE regarding what and how should be tested.
Test instructions: 1. Use GnocchiCorsAllowedOrigin configuration parameter during overcloud deploy. (Example value: "foobar") and enable Gnocchi deploy 2. After deploy, Gnocchi configuration file should contain following configuration in [cors] namespace: allowed_origin=foobar expose_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma max_age=3600 allow_methods=GET,POST,PUT,DELETE,OPTIONS,PATCH allow_headers=Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Auth-Token
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-2020:0760