Bug 2041459 - Three upstream HTTPClientConfig struct fields missing in the operator
Summary: Three upstream HTTPClientConfig struct fields missing in the operator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.z
Assignee: Philip Gough
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 2040694
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-17 11:49 UTC by Philip Gough
Modified: 2023-01-03 11:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2040694
Environment:
Last Closed: 2022-01-24 16:50:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift prometheus-operator pull 148 0 None Merged BUG 2041459: alertmanager: only load cfg when writing cfg 2022-01-19 09:45:55 UTC
Red Hat Knowledge Base (Solution) 6665831 0 None None None 2022-01-25 08:39:16 UTC
Red Hat Product Errata RHBA-2022:0195 0 None None None 2022-01-24 16:50:33 UTC

Comment 1 Junqi Zhao 2022-01-19 02:12:19 UTC
tested with PR, followed steps in Comment 4 and Comment 6 in bug 2040694, no error for http_config.follow_redirects, and no error logs from alertmanager container, we could see the configuration loaded in ${alertmanager_route}/#/status page

Comment 4 Junqi Zhao 2022-01-21 04:30:28 UTC
fix is in 4.9.0-0.nightly-2022-01-19-045232, based on Comment 1, set to verified

Comment 6 errata-xmlrpc 2022-01-24 16:50:18 UTC
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 (OpenShift Container Platform 4.9.17 bug fix update), 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:0195


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