Bug 1891023 - ovn-kubernetes rbac proxy never starts waiting for an incorrect API call
Summary: ovn-kubernetes rbac proxy never starts waiting for an incorrect API call
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Juan Luis de Sousa-Valadas
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks: 1959185
TreeView+ depends on / blocked
 
Reported: 2020-10-23 14:49 UTC by Juan Luis de Sousa-Valadas
Modified: 2021-05-26 09:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:27:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 841 0 None closed Bug 1891023: Fix ovn rbac proxy init script secret name 2021-01-18 08:50:26 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:28:20 UTC

Description Juan Luis de Sousa-Valadas 2020-10-23 14:49:43 UTC
Description of problem:
ovn-kubernetes waits for a service to be created, the problem is that we query for that service incorrectly

Version-Release number of selected component (if applicable):
4.7 only

How reproducible:
always

Steps to Reproduce:
1. launch a 4.7 cluster

Actual results:
metrics don't work

Expected results:
metrics work.

Additional info:

Comment 5 errata-xmlrpc 2021-02-24 15:27:53 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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/RHSA-2020:5633


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