Bug 2093393 - ovn-ipsec pods not rolling out in 4.11.0-0.nightly-2022-06-01-200905 - cannot delete CSR
Summary: ovn-ipsec pods not rolling out in 4.11.0-0.nightly-2022-06-01-200905 - cannot...
Keywords:
Status: CLOSED DUPLICATE of bug 2091167
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.11.0
Assignee: Mohammad Heib
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-03 15:16 UTC by Mike Fiedler
Modified: 2022-06-07 13:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 13:01:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Fiedler 2022-06-03 15:16:09 UTC
Description of problem:

Installs of ipsec profiles are failing in 4.11.0-0.nightly-2022-06-01-200905 because the ovn-ipsec pods are not rolling out.   The error in the the ovn-keys container is:

++ hostname
+ kubectl delete --ignore-not-found=true csr/ip-10-0-62-21
Error from server (Forbidden): certificatesigningrequests.certificates.k8s.io "ip-10-0-62-21" is forbidden: User "system:serviceaccount:openshift-ovn-kubernetes:ovn-kubernetes-node" cannot delete resource "certificatesigningrequests" in API group "certificates.k8s.io" at the cluster scope


Version-Release number of selected component (if applicable): 4.11.0-0.nightly-2022-06-01-200905


How reproducible: Always for ipsec profiles


Additional info:   I will add must-gather location in a follow up comment

Comment 3 Mike Fiedler 2022-06-03 15:30:33 UTC
@mheib Assigning to you, please reassign if appropriate.

Comment 5 Weibin Liang 2022-06-03 16:35:26 UTC
Same error and root cause as" https://bugzilla.redhat.com/show_bug.cgi?id=2091167#c1

Comment 6 Mike Fiedler 2022-06-07 13:01:04 UTC
ipsec profiles are installing ok now

*** This bug has been marked as a duplicate of bug 2091167 ***


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