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

Can't create multiple volumes from the same volume #32

Open
rmb938 opened this issue Jan 28, 2023 · 2 comments
Open

Can't create multiple volumes from the same volume #32

rmb938 opened this issue Jan 28, 2023 · 2 comments
Assignees

Comments

@rmb938
Copy link

rmb938 commented Jan 28, 2023

When creating a volume where the source is a volume. The first creation works, but if I create another volume, it fails.

2023-01-28 22:38:25.687 407797 INFO cinder.volume.drivers.ixsystems.freenasapi [None req-a123df1f-3880-47a7-ae6c-53b9eddba151 fff44df7b41d4fd39edf513ca497a8c4 ba20d749b68045bba695de9dd0123471 - - - -] Error returned from server: "Failed to snapshot tank/vms/volume-abc2c893@snap-cabc2c893: dataset already exists"

The driver tries to create a duplicate snapshot with the same name as the first one.

I believe this is the code that is causing the issue https://github.com/iXsystems/cinder/blob/master/driver/ixsystems/iscsi.py#L286-L287

The name key in temp_snapshot probably should be the volume.id, not referencing the source volume.

@YiHuangDB YiHuangDB self-assigned this Feb 1, 2023
@YiHuangDB
Copy link
Contributor

Hi Ryan, thank you for reporting this issue. I can reproduce the issue on my side. I will let you know once it is fixed. There are actually multiple issues with current snapshot driver implementation, including the code location you point out. We will address that and let you know.

YiHuangDB added a commit to YiHuangDB/cindertruenas that referenced this issue Feb 21, 2023
william-gr added a commit that referenced this issue Feb 27, 2023
@YiHuangDB
Copy link
Contributor

Hi Ryan, this issue has been fixed with PR #33 and merged to master branch, if you have any issue with the fix, technically exactly the same like you mentioned in your post, appreciate your comments and feedbacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants