Bug 1924195

Summary: Service Telemetry Operator fails to retrieve ElasticSearch BasicAuth information from Secret
Product: Red Hat OpenStack Reporter: Leif Madsen <lmadsen>
Component: Service Telemetry FrameworkAssignee: Leif Madsen <lmadsen>
Status: CLOSED CURRENTRELEASE QA Contact: Leonid Natapov <lnatapov>
Severity: urgent Docs Contact:
Priority: high    
Version: unspecifiedCC: augol, mgarciac, mmagr, mrunge, pkilambi, spower
Target Milestone: asyncKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: service-telemetry-operator-container-1.1.0-7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1924355 (view as bug list) Environment:
Last Closed: 2021-02-11 12:44:08 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:    
Bug Blocks: 1924355    

Description Leif Madsen 2021-02-02 18:40:57 UTC
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.

Comment 2 Leif Madsen 2021-02-02 19:53:19 UTC
Moved this to Red Hat OpenStack project since this is targeted to STF 1.1 which is a RHOS-16.0 release component.

Comment 7 Miguel Garcia 2021-02-11 12:44:08 UTC
Build service-telemetry-operator-container-1.1.0-7 is shipped live.