Bug 2129441

Summary: Unable to create access rules 'state:error' | NetApp
Product: Red Hat OpenStack Reporter: swogat pradhan <swogatpradhan22>
Component: openstack-manilaAssignee: OpenStack Manila Bugzilla Bot <openstack-manila-bugs>
Status: CLOSED UPSTREAM QA Contact: vhariria
Severity: unspecified Docs Contact: ndeevy <ndeevy>
Priority: unspecified    
Version: 17.0 (Wallaby)CC: ccopello, gouthamr
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-29 16:01:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description swogat pradhan 2022-09-23 19:17:00 UTC
Description of problem:
When i am trying to create access rule for manila share, the rules are created in error state.

Version-Release number of selected component (if applicable):
wallaby

How reproducible:
create share access rule

Steps to Reproduce:
1.install manila
2.Create share
3.Create access rule

Actual results:
Access rules are in error state:
Here is the manila share log:
2022-09-23 19:03:58.557 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status
2022-09-23 19:04:01.720 26 INFO manila.share.manager [req-3d66c534-a782-414b-a0a7-2bdd57f57b8f - - - - -] Updating share status
2022-09-23 19:04:58.554 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server [req-5f035b4a-7dc8-4e61-bbd5-d38d4b81a00d c1905e3c5a374924980e851840e7f028 5d922243077045c48fe4b075e386551b - - -] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 216, in wrapped
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/utils.py", line 568, in wrapper
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3965, in update_access
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server_id=share_server_id)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3981, in update_access_for_instances
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 302, in update_access_rules
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 341, in _update_access_rules
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 409, in _update_rules_through_share_driver
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/drv_single_svm.py", line 104, in update_access
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server delete_rules, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py", line 2347, in update_access
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server helper.update_access(share, share_name, access_rules)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 36, in wrapped_func
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return source_func(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(*args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 34, in source_func
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 115, in update_access
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server auth_methods = self._get_auth_methods()
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 222, in _get_auth_methods
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server kerberos_enabled = self._client.is_kerberos_enabled()
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_cmode.py", line 1896, in is_kerberos_enabled
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = self.send_request('kerberos-config-get', api_args)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_base.py", line 90, in send_request
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server use_zapi=use_zapi)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 710, in invoke_successfully
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server na_element, api_args=api_args, enable_tunneling=enable_tunneling)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 380, in invoke_successfully
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server raise NaApiError(code, msg)
2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist

Expected results:
Access rule should be successfully created

Additional info:

Comment 1 Goutham Pacha Ravi 2022-09-24 00:19:13 UTC
Hi Swogat, 

Thanks for reporting this bug. I see that you're using the "Wallaby" release of OpenStack Manila. We don't (yet) support this release with Red Hat OpenStack Platform. Are you using a different RHOSP version? Or perhaps the community edition of the code? If it is the latter, the right place to report the bug would be: https://bugs.launchpad.net/manila

Comment 2 swogat pradhan 2022-09-24 09:55:01 UTC
Hi,
Thank you for responding. I have raised the issue in launchpad : https://bugs.launchpad.net/manila/+bug/1990693
Can you atleast tell me which side to look at? if it's the problem from manila side or problem in configuration in netapp side.

Comment 3 Goutham Pacha Ravi 2022-09-29 16:01:09 UTC
(In reply to swogat pradhan from comment #2)
> Hi,
> Thank you for responding. I have raised the issue in launchpad :
> https://bugs.launchpad.net/manila/+bug/1990693
> Can you atleast tell me which side to look at? if it's the problem from
> manila side or problem in configuration in netapp side.

It could be either - the best folks to answer that would be driver maintainers of NetApp in the community; thanks for engaging upstream via https://bugs.launchpad.net/manila/+bug/1990693 - the driver maintainers are now aware, and they're responding to your bug report. I'm closing this BZ as an upstream issue; we'll continue the discussion upstream.