Bug 1924195 - Service Telemetry Operator fails to retrieve ElasticSearch BasicAuth information from Secret
Summary: Service Telemetry Operator fails to retrieve ElasticSearch BasicAuth informat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: Service Telemetry Framework
Version: unspecified
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: async
: ---
Assignee: Leif Madsen
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 1924355
TreeView+ depends on / blocked
 
Reported: 2021-02-02 18:40 UTC by Leif Madsen
Modified: 2021-02-11 12:44 UTC (History)
6 users (show)

Fixed In Version: service-telemetry-operator-container-1.1.0-7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1924355 (view as bug list)
Environment:
Last Closed: 2021-02-11 12:44:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github infrawatch service-telemetry-operator pull 170 0 None closed Resolve issue with ElasticSearch password retrieval 2021-02-21 08:30:08 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.