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

Incorrect response from nfs_share create() call #333

Closed
v-soni11 opened this issue Nov 4, 2020 · 3 comments
Closed

Incorrect response from nfs_share create() call #333

v-soni11 opened this issue Nov 4, 2020 · 3 comments
Assignees
Labels

Comments

@v-soni11
Copy link

v-soni11 commented Nov 4, 2020

Issue: Incorrect response from nfs_share create() call

Description: When we have two filesystems with same name on different NAS, and then we try to create NFS on both the filesystems with same name, nfs_share.py create() function returns wrong/different nfs share object.

Steps to reproduce the issue:

  1. create filesystem 'abc' on nasserver 'lglad071'
  2. create filesystem 'abc' on nasserver 'lglad069'
  3. create NFS 'test_nfs' from filesystem 'abc' which is on nasserver 'lglad071'
  4. create NFS 'test_nfs' from filesystem 'abc' which is on nasserver 'lglad069' using below code snippet:
from storops.unity.resource import nfs_share
from storops import UnitySystem

# Create connection object
>>> conn = UnitySystem('xx.xx.xx.xx', 'username', 'password', verify=False)

# Get NAS object
>>> nas_obj = conn.get_nas_server(name="lglad069")

# Get Filesystem object
>>> fs = conn.get_filesystem(name="abc", nas_server=nas_obj)

# Create NFS Share
>>> nfs = nfs_share.UnityNfsShare.create(conn._cli, "test_nfs", fs)

# Validate created NFS Share 
>>> nfs.filesystem.nas_server.name # should return 'lglad069'
'lglad071'

nfs_share.create() call returns wrong/different nfs_share obj whose name is same as we gave in create(name=''test_nfs) parameter

@yong-huang yong-huang self-assigned this Nov 5, 2020
@yong-huang yong-huang added the bug label Nov 11, 2020
@yong-huang
Copy link
Contributor

Root caused, will fix it.

@yong-huang
Copy link
Contributor

Fixed in #335

@v-soni11
Copy link
Author

Verified and its working fine now
Thanks

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

No branches or pull requests

2 participants