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.
Also in vSphere: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.3/365
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.
https://github.com/openshift/origin/pull/24181
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