Bug 1813233

Summary: openshift-controller-manager-operator/openshift-controller-manager endpoints are down on ipv6 cluster
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: openshift-controller-managerAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: wewang <wewang>
Severity: urgent Docs Contact:
Priority: medium    
Version: 4.3.zCC: anikifor, aos-bugs, avicenzi, inecas, mfojtik, rvokal, wewang, wzheng
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Controller manager operator was not exposing its metrics when over an ipv6 cluster. Consequence: Metrics were not being properly scraped, leaving the user with no way to graph or query performance data. Fix: By updating a vendored package the operator now binds to ipv6 interfaces. Result: Metrics are scrapped correctly and presented to the user.
Story Points: ---
Clone Of: 1813232
: 1819770 (view as bug list) Environment:
Last Closed: 2020-07-13 17:19:58 UTC Type: ---
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: 1819770    
Attachments:
Description Flags
down endpoints in 4.3 ipv6 cluster
none
openshift-controller-manager endpoints are down on 4.4 ipv6 cluster none

Comment 1 Junqi Zhao 2020-03-13 10:56:45 UTC
Created attachment 1669892 [details]
down endpoints in 4.3 ipv6 cluster

Comment 4 Junqi Zhao 2020-03-24 08:45:58 UTC
Created attachment 1672968 [details]
openshift-controller-manager endpoints are down on 4.4 ipv6 cluster

Comment 5 Ricardo Maraschini 2020-04-08 09:48:12 UTC
*** Bug 1816948 has been marked as a duplicate of this bug. ***

Comment 11 wewang 2020-05-13 12:03:54 UTC
@Ricardo ipv6 cluster is provided by Edge team before, I am asking them if have 4.5 env can be used to test.

Comment 19 errata-xmlrpc 2020-07-13 17:19:58 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, 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:2409