-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
I believe https://github.com/openshift/insights-operator/pull/607/ has broken payloads. Specifically the image reference to kube-rbac-proxy: it's being pulled from quay instead of the release payload! I believe it shopuld be registry.ci.openshift.org/openshift:kube-rbac-proxy and added to the image-references file.
e2e-metal-ipi-ovn-ipv6 started failing in https://amd64.ocp.releases.ci.openshift.org/releasestream/4.11.0-0.nightly/release/4.11.0-0.nightly-2022-06-02-202024 blocking payloads on `[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state`
alert KubeContainerWaiting fired for 2955 seconds with labels: {container="kube-rbac-proxy", namespace="openshift-insights", pod="insights-operator-94b79c48c-m8gmq", severity="warning"} alert KubeDeploymentReplicasMismatch fired for 4294 seconds with labels: {container="kube-rbac-proxy-main", deployment="insights-operator", endpoint="https-main", job="kube-state-metrics", namespace="openshift-insights", service="kube-state-metrics", severity="warning"} alert TargetDown fired for 4294 seconds with labels: {job="metrics", namespace="openshift-insights", service="metrics", severity="warning"}}
CI search shows this is a new problem:
