-
Notifications
You must be signed in to change notification settings - Fork 42
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
Getting a single LUN mapping #40
Comments
Thank you for reporting an issue! If you haven't already joined our Discord community, |
Hello, It would be very helpful to know what the requests and responses from your example look like. Can you please enabled debug logging and share the output. You can do that by including this in your script: import logging
from netapp_ontap import config, utils
utils.LOG_ALL_API_CALLS = 1
utils.DEBUG = 1
logging.basicConfig(level=logging.DEBUG) Just by looking at your code, I can think of couple possible issues. mapresource = LunMap({'igroup.name': 'myig', 'lun.uuid': '8f27a86c-8c79-4d94-ab22-e86868954d5c'})
mrs = mapresource.get() The above code is incorrect. The library expects path keys ( To fix this, you should restructure the code to this: mapresource = LunMap(myig, 8f27a86c-8c79-4d94-ab22-e86868954d5c)
mapresource.get() As for the second example, you're making an incorrect request because
Please let me know if this helps. -Noor |
Interesting, thank you for elaborating on this! I'll try to test your suggestions and report back soon, if needed with the debug output. |
Hi,
I am trying to retrieve a a LUN mapping resource for a single specific LUN.
get()
on a LunMap with a filter which should only match a single entry results in an error:And
get_collection()
results in a large amount of unrelated mappings:Same results if using
lun.name
or evenlogical_unit_number
:I would expect to retrieve only one mapping result if a distinct filter is specified. Am I missing something?
Edit: this is against ONTAP 9.9 with the libraries netapp-lib 2021.6.25 and netapp-ontap 9.13.1.0.
The text was updated successfully, but these errors were encountered: