Description of problem: The Service Telemetry Operator fails to retrieve the contents of the ElasticSearch BasicAuth password in the most recent re-spin of the Service Telemetry Operator for STF 1.1. Version-Release number of selected component (if applicable): service-telemetry-operator-container-1.1.0 How reproducible: Every time Steps to Reproduce: 1. run service-telemetry-operator 2. create ServiceTelemetry object with ElasticSearch enabled 3. note failure at Filter out ElasticSearch password for BasicAuth] Actual results: TASK [servicetelemetry : Filter out ElasticSearch password for BasicAuth] ****** task path: /opt/ansible/roles/servicetelemetry/tasks/component_clouds.yml:32 fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"} Expected results: No failure. Additional info: The same code exists upstream as downstream, but the parent image seems to have changed between upstream and downstream. Both upstream and downstream are using the operator-sdk v0.16.0 images for ose-ansible-operator (or quay.io/operator-framework/ansible-operator for upstream), but the downstream image uses ansible version 2.9.17 vs upstream image using 2.9.6. There appears to be some regression in the downstream base image which has likely been bumped to another RHEL7 parent image due to CVE and image rebuilds.
Moved this to Red Hat OpenStack project since this is targeted to STF 1.1 which is a RHOS-16.0 release component.
Build service-telemetry-operator-container-1.1.0-7 is shipped live.