Volume From Snapshot Fails With Custom Node Ids #541
Labels
enhancement
Add new functionality to existing feature
Need community involvement
Needs community involvement on some action item.
waiting for contributor
Waiting on the contribution from the community contributor.
What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.]
openebs.io/nodeid
What did you expect to happen:
It should utilize the correct ids when identifying the node and create the volume from snapshot successfully.
Anything else you would like to add:
We pre-label (before starting zfs components) our nodes with unique identifiers for
openebs.io/nodeid
and these identifiers differ from the node name.With this configuration, I am able to create new ZFS volumes without issue. However, when you attempt to create a zfs volume from a snapshot definition it fails.
In the logs I can see
failed to get the node {VALUE_OF_OPENEBS_NODEID}
which highlights the issue. ThisGetNodeID
method involume.go
only works when it is passed the nodename.In the case of creating a new volume
GetNodeID
is called with the nodename but when it is from a volume clone or a snapshot it gets called with the value ofopenebs.io/nodeid
. This is because this block here indriver/controller.go
in theCreateVolume
method:CreateSnapClone
--> returns spec.OwnerNodeIdCreateVolClone
--> returns spec.OwnerNodeIdCreateZFSVolume
--> returns nodename loop variableEnvironment:
kubectl version
): 1.29/etc/os-release
):The text was updated successfully, but these errors were encountered: