Bug 2040710
| Summary: | cluster-baremetal-operator cannot update BMC subscription CR | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Honza Pokorny <hpokorny> |
| Component: | Installer | Assignee: | Honza Pokorny <hpokorny> |
| Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Ori Michaeli <omichael> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | omichael |
| Version: | 4.10 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | 4.10.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: | 2022-03-10 16:39:37 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: | |||
Verified using 4.10.0-0.nightly-2022-01-16-191814 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056 |
bmceventsubscriptions.metal3.io "sub-01" is forbidden: User "system:serviceaccount:openshift-machine-api:cluster-baremetal-operator" cannot update resource "bmceventsubscriptions/status" in API group "metal3.io" in the namespace "openshift-machine-api" failed to update subscription status github.com/metal3-io/baremetal-operator/controllers/metal3%2eio.(*BMCEventSubscriptionReconciler).handleError /go/src/github.com/metal3-io/baremetal-operator/controllers/metal3.io/bmceventsubscription_controller.go:137 github.com/metal3-io/baremetal-operator/controllers/metal3%2eio.(*BMCEventSubscriptionReconciler).Reconcile /go/src/github.com/metal3-io/baremetal-operator/controllers/metal3.io/bmceventsubscription_controller.go:118 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler /go/src/github.com/metal3-io/baremetal-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:298 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem /go/src/github.com/metal3-io/baremetal-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:253 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 /go/src/github.com/metal3-io/baremetal-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:214 runtime.goexit /usr/lib/golang/src/runtime/asm_amd64.s:1581 This is caused by a misnamed resource in the RBAC rules: bmceventsubscriptions/status vs bmceventsubscription/status