the creation of "share access" no longer works since migrating to OpenStack Wallaby

[Mohit Laungani]

error message :
Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API
failed. Reason - 15661:entry doesn't exist

Backend configuration :
[netappNFS]
share_backend_name = NETAPPNFS
share_driver =
manila.share.drivers.netapp.common.NetAppDriver
driver_handles_share_servers = False
netapp_storage_family =
ontap_cluster
netapp_server_hostname = svmtaff400-opk31-nfs
netapp_server_port = 443
netapp_login = opkbas
netapp_password =
**********
netapp_vserver = svmtaff400-opk-bas31-nfs
netapp_transport_type = https
netapp_aggregate_name_search_pattern =
^((?!aggr0).)*$

- This is also a dedicated vServer used for Manila
- Previously was working fine with Victoria

Based on some testing in the lab using an Openstack Kolla-Ansible release, I have found that it works when using the cluster admin credentials that are defined in the manila.conf configuration file. I have the same issue with the customer when I try to run the command "manila access-allow" using the vsadmin user and password.

[Vida Haririan (vhariria)]

See additional discussions at https://meetings.opendev.org/meetings/manila/2024/manila.2024-01-18-15.00.log.html

[Vida Haririan (vhariria)]

See additional triage information at https://meetings.opendev.org/meetings/manila/2024/manila.2024-01-25-15.00.log.html

[Saravanan Manickam (msaravan)]

Is the same SVM used for any of the cinder workflows ?

Can you list the LIFs present in your SVM ? Would like to see what protocols enabled on them ?

Can you try to have a dedicated SVM with only NFS enabled, and repeat the workflow ?

Please share the full log of manila (with trace enabled) and commands along with that.