GetNodeID failed for node #493
Labels
kind/bug
Categorizes issue or PR as related to a bug
Comments
|
Can you please check PR #451 . It has the way how to set the labels for node. |
|
closing because i never reproduced it |
|
reopening since it re-appeared when adding a node to an existing cluster. i manually labeled the node as but that did nothing looking at the code i'm not even sure why that would be related the error returned here is just eaten, so we cant see the cause |
aep
added a commit
to aep/zfs-localpv
that referenced
this issue
May 19, 2024
this is issue openebs#493 when zfs-localpv is broken due to an k8s api issue, it just says 'GetNodeID failed for node'. this change adds the actual api error Signed-off-by: Arvid E. Picciani <[email protected]>
aep
added a commit
to aep/zfs-localpv
that referenced
this issue
May 19, 2024
Fixes issue openebs#493 when zfs-localpv is broken due to an k8s api issue, it just says 'GetNodeID failed for node'. this change adds the actual api error Signed-off-by: Arvid E. Picciani <[email protected]>
Abhinandan-Purkait
pushed a commit
that referenced
this issue
May 22, 2024
Fixes issue #493 when zfs-localpv is broken due to an k8s api issue, it just says 'GetNodeID failed for node'. this change adds the actual api error Signed-off-by: Arvid E. Picciani <[email protected]>
|
@aep were you able to figure out the reason once your fix went in? |
|
Yes. Showing the actual error allowed me to find out it's a K8s API server issue. This can be closed. |
|
Glad to know it helped !! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when adding a node to StorageClass.allowedTopologies , nothing appears to create the matching zfsnode.zfs.openebs.io
the openebs-zfs-node pod is started but crashes with
in testing, this recovers when deleting all pvc and storageclass.
The text was updated successfully, but these errors were encountered: