Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: openebs-zfs-plugin: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io #441

Open
Subetov opened this issue May 17, 2023 · 1 comment
Assignees
Labels
backlog Will be picked up as a roadmap item. need more info More information is needed from user, need reproduction steps waiting for contributor Waiting on the contribution from the community contributor.

Comments

@Subetov
Copy link

Subetov commented May 17, 2023

What steps did you take and what happened:
A large number of similar errors in the logs of zfs-localpv-node pod.

openebs-zfs-plugin E0517 11:56:59.878576       1 zfsnode.go:279] error syncing 'kube-system/some-node': update zfs node kube-system/some-node: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io "some-node": the object has been modified; please apply your changes to the latest version and try again, requeuing
openebs-zfs-plugin E0517 11:57:16.284629       1 zfsnode.go:279] error syncing 'kube-system/some-node': update zfs node kube-system/some-node: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io "some-node": the object has been modified; please apply your changes to the latest version and try again, requeuing
openebs-zfs-plugin E0517 11:57:32.716366       1 zfsnode.go:279] error syncing 'kube-system/some-node': update zfs node kube-system/some-node: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io "some-node": the object has been modified; please apply your changes to the latest version and try again, requeuing
openebs-zfs-plugin E0517 11:57:48.973489       1 zfsnode.go:279] error syncing 'kube-system/some-node': update zfs node kube-system/some-node: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io "some-node": the object has been modified; please apply your changes to the latest version and try again, requeuing
openebs-zfs-plugin E0517 11:58:13.618259       1 zfsnode.go:279] error syncing 'kube-system/some-node': update zfs node kube-system/some-node: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io "some-node": the object has been modified; please apply your changes to the latest version and try again, requeuing

I'm not 100% sure, but it seems to me that the error is related to the fact that there are too many requests to change the "zfsnodes.zfs.openebs.io" resource. (constantly changes the amount of free disk space)
Perhaps it depends on the load of the system.

What did you expect to happen:
No such errors.

The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other Pastebin is fine.)

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

  • ZFS-LocalPV version: chart: zfs-localpv-1.9.7 appVer: 1.9.1
  • Kubernetes version (use kubectl version): v1.24.8+k3s1
@Subetov Subetov changed the title [Bug]: **openebs-zfs-plugin**: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io [Bug]: openebs-zfs-plugin: Operation cannot be fulfilled on zfsnodes.zfs.openebs.io May 17, 2023
@niladrih niladrih self-assigned this Sep 13, 2023
@Abhinandan-Purkait
Copy link
Member

@niladrih Do you have any update on this. Seems like you have self assigned yourself.

@Abhinandan-Purkait Abhinandan-Purkait added backlog Will be picked up as a roadmap item. need more info More information is needed from user, need reproduction steps waiting for contributor Waiting on the contribution from the community contributor. labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Will be picked up as a roadmap item. need more info More information is needed from user, need reproduction steps waiting for contributor Waiting on the contribution from the community contributor.
Projects
None yet
Development

No branches or pull requests

3 participants