Bug 1724091 - "Cannot update endpoints in namespace" error after deploying gluster block provisioner pod
Summary: "Cannot update endpoints in namespace" error after deploying gluster block pr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-deploy-tool
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: Saravanakumar
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-26 08:47 UTC by RamaKasturi
Modified: 2023-09-14 05:30 UTC (History)
9 users (show)

Fixed In Version: cns-deploy-7.0.0-13.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1723366
Environment:
Last Closed: 2019-10-30 12:33:52 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3254 0 None None None 2019-10-30 12:33:59 UTC

Comment 3 Saravanakumar 2019-06-26 10:32:41 UTC 
Upstream PR:
https://github.com/gluster/gluster-kubernetes/pull/285 


Changes are merged into downstream and available in cns-deploy-7.0.0-13.el7rhgs
Comment 5 RamaKasturi 2019-07-01 12:38:30 UTC 
Verified in the build cns-deploy-7.0.0-13.el7rhgs.x86_64.

I see that the glusterblock-provisioner template has been updated with the below details.

- apiGroups: [""]
      resources: ["endpoints"]
      verbs: ["get", "list", "watch", "create", "update", "patch"]

Block volume creation works and do not see any errors in the oc logs <block_provisioner_pod>.

[root@dhcp47-179 templates]# oc get pvc
NAME      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
test      Bound     pvc-6fa61668-9bf1-11e9-a030-005056b200f5   1Gi        RWO            glusterfs-block   1h
test1     Bound     pvc-7accad62-9bf1-11e9-a030-005056b200f5   10Gi       RWO            glusterfs-block   1h
Comment 9 errata-xmlrpc 2019-10-30 12:33:52 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, 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/RHBA-2019:3254
Comment 10 Red Hat Bugzilla 2023-09-14 05:30:55 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.