Skip to main content
NetApp Knowledge Base

OpenStack: Manila fails to set up share access due to a "NetApp API failed" exception

  1. Last updated
  2. Save as PDF
Views:
99
Visibility:
Public
Votes:
0
Category:
openstack
Specialty:
VIRT
Last Updated:

Applies to

  • OpenStack Manila
  • DHSS = False

Issue

When Manila is configured to use a SVM scoped user for it's share service backend, the following issue is seen when you attempt to create access for a share (using the  manila access-allow command)

  • The manila share.log displays the following API exception:

33344: 2024-06-11 11:36:47.019 1360587 ERROR oslo_messaging.rpc.server [req-12345676] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist

  • When tracing the API calls during the timestamp of the issue, you see the following kerberos-config-get-iter API call fail:

00000015.006cad50 06cd461e Wed Jul 03 2024 13:22:27 +00:00 [kern_audit:info:3328] 8503e800003f7318 :: ontap:ontapi :: xx.xx.xx.xx:39724 :: xxxxx:manilauser :: <netapp xmlns=http://www.netapp.com/filer/admin version="1.231" vfiler="xxxxx"><kerberos-config-get><interface-name>xxxxx-mgmt</interface-name><desired-attributes><kerberos-config-info><is-kerberos-enabled/></kerberos-config-info></desired-attributes></kerberos-config-get></netapp> :: Pending: 

00000015.006cad52 06cd461e Wed Jul 03 2024 13:22:27 +00:00 [kern_audit:info:3328] 8503e800003f7318 :: ontap:ontapi :: xx.xx.xx.xx:39724 :: xxxxx:manilauser :: kerberos-config-get :: Error: entry doesn't exist
 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.