Closed jacobbaungard closed 1 week ago
/cherry-pick release-2.12
@jacobbaungard: once the present PR merges, I will cherry-pick it on top of release-2.12
in a new PR and assign it to you.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jacobbaungard, thibaultmg
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
/retest
/retest
/retest
/retest
/retest
@jacobbaungard: new pull request could not be created: failed to create pull request against stolostron/multicluster-observability-operator#release-2.12 from head openshift-cherrypick-robot:cherry-pick-1661-to-release-2.12: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between stolostron:release-2.12 and openshift-cherrypick-robot:cherry-pick-1661-to-release-2.12"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}
During upgrade from ACM2.11->ACM2.12 for a (currently not fully understood reason) we use the proxy image from the base templates. This seem to happen only for a short while, on later reconciles we appear get the correct image from the OCP imagestream.
The image previously set in the base template were amd64 only, causing the pods to crash on any other architecture. From rbac-query-proxy and Grafana it eventually resolves, however alertmanager uses a stateful set and gets stuck due the known Kubernetes issue described here: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#forced-rollback
Ideally we'd never want to use these images, but meanwhile this should at least ensure we don't crash and leave a unhealthy stateful set for alertmanager.