Bug 1774352 - Installation fails with co/monitoring not available due to 'Alertmanager.monitoring.coreos.com "main" is invalid: type: Required value'
Summary: Installation fails with co/monitoring not available due to 'Alertmanager.moni...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-20 05:27 UTC by Xingxing Xia
Modified: 2020-01-23 11:13 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:13:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24181 0 'None' closed Bug 1774352: Update deps to resolve problems between golang.org/x/crypto and golang.org/x/sys 2020-06-18 05:28:45 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:13:36 UTC

Comment 4 Yuxiang Zhu 2019-11-20 13:31:51 UTC
Looks like 4.3 nighties are synced as normal.

I don’t have any background knowledge about this, but the error message seems to indicate an invalid format with the `main` Alertmanager resource.
Someone should probably look at the CRD of Alertmanager and verify the `main` Alertmanager resource matches the CRD and is in latest version.

Comment 6 Yuxiang Zhu 2019-11-20 14:09:50 UTC
OK, I did a lot of checks, and found the ose repo were not synced into http://pkgs.devel.redhat.com/cgit/containers/ose-openshift-apiserver/log/?h=rhaos-4.3-rhel-7 for some reason. I noticed there are already tags for newer releases in github.com/openshift/ose but they are not in the internal repo.
We need to fix that.

Comment 10 Eric Paris 2019-11-20 16:23:10 UTC
https://github.com/openshift/origin/pull/24181

Comment 14 errata-xmlrpc 2020-01-23 11:13:20 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:0062


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