Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1774352

Summary: Installation fails with co/monitoring not available due to 'Alertmanager.monitoring.coreos.com "main" is invalid: type: Required value'
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: openshift-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: alegrand, anpicker, aos-bugs, crawford, erooth, jcallen, jokerman, juzhao, kakkoyun, lcosic, mfojtik, mloibl, pkrupa, surbania, yuxzhu
Target Milestone: ---Keywords: Regression
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:13:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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