Bug 2023604 - ACL violation when deleting a provisioning-configuration resource
Summary: ACL violation when deleting a provisioning-configuration resource
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: sdasu
QA Contact: Adina Wolff
URL:
Whiteboard:
Depends On:
Blocks: 1991641
TreeView+ depends on / blocked
 
Reported: 2021-11-16 06:52 UTC by Adina Wolff
Modified: 2022-03-10 16:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:27:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-baremetal-operator pull 216 0 None open Bug 2023604: Allow validatingwebhookconfigurations to delete Provisioning CR 2021-11-16 14:54:48 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:27:59 UTC

Description Adina Wolff 2021-11-16 06:52:04 UTC
Description of problem:
In OCP 4.10, when attempting to delete provisioning provisioning-configuration, a message is shown 'provisioning.metal3.io "provisioning-configuration" deleted', but the command does not return and the provisioning is not deleted.

Version-Release number of selected component (if applicable):
4.10.0-0.nightly-2021-11-15-034648

How reproducible:
100%

Steps to Reproduce:

In provisionhost, run the following;
[kni@provisionhost-0-0 ~]$ oc delete provisioning provisioning-configuration
provisioning.metal3.io "provisioning-configuration" deleted
^C


Actual results:

command does not stop until it's killed (ctrl+c)
and the following statuses are showsn;
[kni@provisionhost-0-0 ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2021-11-15-034648   True        False         11h     Error while reconciling 4.10.0-0.nightly-2021-11-15-034648: the cluster operator baremetal is degraded
[kni@provisionhost-0-0 ~]$ ^C
[kni@provisionhost-0-0 ~]$ oc get provisioning
NAME                         AGE
provisioning-configuration   12h
[kni@provisionhost-0-0 ~]$ oc get clusteroperator baremetal
NAME        VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
baremetal   4.10.0-0.nightly-2021-11-15-034648   True        True          True       12h     failed to delete metal3 resource: failed to delete validatingwebhook and service: validatingwebhookconfigurations.admissionregistration.k8s.io "baremetal-operator-validating-webhook-configuration" is forbidden: User "system:serviceaccount:openshift-machine-api:cluster-baremetal-operator" cannot delete resource "validatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
[kni@provisionhost-0-0 ~]$ 


Expected results:
provisioning is deleted successfully. command ends. 
clusteroperator baremetal shows appropriate message (waiting for provisioning)

Comment 3 Adina Wolff 2021-11-24 11:53:07 UTC
Tested on OCP 4.10.0-0.nightly-2021-11-24-030137
provisioning can be deleted:

[kni@provisionhost-0-0 ~]$ oc get provisioning provisioning-configuration -o yaml >prov.yaml
[kni@provisionhost-0-0 ~]$ oc delete provisioning provisioning-configuration
provisioning.metal3.io "provisioning-configuration" deleted
[kni@provisionhost-0-0 ~]$ oc get provisioning provisioning-configuration
Error from server (NotFound): provisionings.metal3.io "provisioning-configuration" not found
[kni@provisionhost-0-0 ~]$

Comment 6 errata-xmlrpc 2022-03-10 16:27:31 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 (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


Note You need to log in before you can comment on or make changes to this bug.