Bug 1990932 - Whereabouts fails in 4.9 due to missing RBAC for leases
Summary: Whereabouts fails in 4.9 due to missing RBAC for leases
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
: 2017983 (view as bug list)
Depends On: 1990928
TreeView+ depends on / blocked
Reported: 2021-08-06 15:29 UTC by Douglas Smith
Modified: 2021-11-22 17:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1990928
Last Closed: 2021-10-20 19:33:06 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1186 0 None open Bug 1990932: [Backport 4.7] Whereabouts should have RBAC for leases 2021-10-06 15:24:21 UTC
Red Hat Product Errata RHBA-2021:3824 0 None None None 2021-10-20 19:33:19 UTC

Description Douglas Smith 2021-08-06 15:29:00 UTC
+++ This bug was initially created as a clone of Bug #1990928 +++

+++ This bug was initially created as a clone of Bug #1989734 +++

Description of problem: Whereabouts fails

Version-Release number of selected component (if applicable): 4.9

How reproducible: Always.

Steps to Reproduce:
1. Create net-attach-def using whereabouts, such as:

apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
  name: macvlan-conf
  config: '{
      "cniVersion": "0.3.0",
      "type": "macvlan",
      "master": "ens4",
      "mode": "bridge",
      "ipam": {
        "type": "whereabouts",
        "range": ""

2. Create some pods that reference it:


3. If the pods do not come up, you've encountered it. If the pods come up, it's working.

Actual results: Pods don't come up.

Expected results: Pods come up (with properly assigned IPs)

--- Additional comment from Douglas Smith on 2021-08-03 20:03:39 UTC ---

Missing from step #2 above:

apiVersion: apps/v1
kind: ReplicaSet
  name: whereabouts-test
    app: whereabouts-test
    tier: whereabouts-test
  # modify replicas according to your case
  replicas: 3
      tier: whereabouts-test
        tier: whereabouts-test
        k8s.v1.cni.cncf.io/networks: macvlan-conf
      - name: samplepod
        command: ["/bin/ash", "-c", "trap : TERM INT; sleep infinity & wait"]
        image: quay.io/dougbtv/alpine:latest

Comment 1 Weibin Liang 2021-10-07 21:00:36 UTC
[weliang@weliang tmp]$ oc get pods
NAME                                  READY   STATUS    RESTARTS   AGE
multus-macvlan-pod-644b94f5f9-6sltm   1/1     Running   0          20s
multus-macvlan-pod-644b94f5f9-vk6ww   1/1     Running   0          20s
multus-macvlan-pod-644b94f5f9-xrvj9   1/1     Running   0          20s
[weliang@weliang tmp]$ oc get clusterversion
NAME      VERSION                                                  AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.ci.test-2021-10-07-201640-ci-ln-j3zcr4k-latest   True        False         8m41s   Cluster version is 4.7.0-0.ci.test-2021-10-07-201640-ci-ln-j3zcr4k-latest
[weliang@weliang tmp]$

Comment 6 errata-xmlrpc 2021-10-20 19:33:06 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 (OpenShift Container Platform 4.7.34 bug fix 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.


Comment 7 Douglas Smith 2021-10-28 17:47:53 UTC
*** Bug 2017983 has been marked as a duplicate of this bug. ***

Comment 8 Lucas López Montero 2021-11-05 15:09:11 UTC
We have a production cluster on version 4.7.33 experiencing this problem, we have manually configured RBAC as described on the pull request [1] as a workaround and it works. So far so good. 

However; when we upgrade to 4.7.34 or a later version, I would assume there will be an "AlreadyExists" error because the RBAC configuration has been already set. Is this correct? Will that imply any problem during or after the eventual upgrade to 4.7.34 (or later)?

Thank you for your help.

[1] https://github.com/openshift/cluster-network-operator/pull/1186/files#diff-527b1b0eb2d5eb12b3830bbc2a3c834c62e447cdab04f0f080d57b27e34f4933

Comment 9 Douglas Smith 2021-11-05 15:20:21 UTC
Lucas -- I believe the cluster-network-operator should be able to reconcile the objects that it templates. That is, the cluster-network-operator should account for already existing resources and update them (or leave them alone if they match). 

So I don't believe it should be a problem to leave those custom-created RBAC rules for the work, such as those you've created which are similar/the same as those patch that you've linked.

Comment 10 Lucas López Montero 2021-11-05 17:06:57 UTC
Thank you very much for the clarification, Douglas.

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