Bug 1829072 - OLM installation with with a stage build failed due to invalid url (space in url name)
Summary: OLM installation with with a stage build failed due to invalid url (space in...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Metering Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: tflannag
QA Contact: Peter Ruan
Depends On:
Blocks: 1829035
TreeView+ depends on / blocked
Reported: 2020-04-28 20:17 UTC by tflannag
Modified: 2020-07-13 17:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1829035
Last Closed: 2020-07-13 17:32:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github kube-reporting metering-operator pull 1198 0 None closed Bug 1829072: Remove all instances of the k8s_event module. 2020-06-24 01:27:58 UTC
Github kube-reporting metering-operator pull 1203 0 None closed Bug 1829072: Fix all of the k8s_event module instances. 2020-06-24 01:27:56 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:32:47 UTC

Comment 2 Ben Parees 2020-05-11 18:16:15 UTC
This was "fixed" by disabling a bunch of things.  That's fine for 4.4 where they weren't needed and disabling them was the simplest path to fixing the issue, but for 4.5 we need to ensure it gets fixed properly w/ the features enabled.

Whether we do that via this bug or a separate tracking bug.

Comment 3 Ben Parees 2020-05-11 18:17:29 UTC
From Tim:
The presto-prometheus connector, which is what the next issue was about in 1829035 was also removed entirely and has no real value being in 4.4. I'm running into some snaps getting that working in 4.5

Comment 7 Peter Ruan 2020-06-09 04:37:38 UTC
verified with 4.4 zstream stage build

Comment 8 errata-xmlrpc 2020-07-13 17:32:29 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.


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