Bug 1861084

Summary:	manila-share container is failing to intialize on startup with a NetApp as the backend target
Product:	Red Hat OpenStack	Reporter:	Tim Quinlan <tquinlan>
Component:	openstack-manila	Assignee:	Goutham Pacha Ravi <gouthamr>
Status:	CLOSED ERRATA	QA Contact:	vhariria
Severity:	high	Docs Contact:	mmurray
Priority:	high
Version:	13.0 (Queens)	CC:	ahyder, ccopello, gouthamr, igallagh, vimartin
Target Milestone:	z13	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-manila-6.3.2-4.el7ost	Doc Type:	Bug Fix
Doc Text:	Before this update, if the OpenStack Shared File Systems (manila) service was configured with VServer-scoped ONTAP credentials it caused share provisioning to fail. This was due to a recent change to the NetApp ONTAP driver causing the share manager service to become stuck in a restart loop while trying to determine the storage system capabilities. With this update, the NetApp ONTAP driver now checks for Vserver-scoped NetApp users and adds a fall-back path for determining storage system capabilities, which resolves the issue. The OpenStack Shared File Systems share manager service can now successfully determine the storage system capabilities, and share provisioning succeeds.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-28 18:26:58 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 Tim Quinlan 2020-07-27 18:38:44 UTC

Description of problem:

[NetApp] Fix svm scoped account

When the NetApp backend starts, it needs to know whether the
`revert_to_snapshot` support exist. So, it was retrieving the
licenses and checking if the `SnapRestore` is included. Using a
scoped account, the backend cannot retrieve that information,
though. So, this patch solves it by sending a fake operation
`revert_to_snapshot` that must fail. Analyzing the given error, it
sets the backend support field.

How reproducible:
Always

Steps to Reproduce:
1. Configure manila to use a Netapp account that is SVM scoped

Actual results:
2020-05-29 19:10:11.310 28 INFO manila.share.drivers.netapp.dataontap.cluster_mode.lib_single_svm [req-7d2820bd-cff1-4318-88ca-3bae02c492f9 - - - - -] Using Vserver shksvmpfws03 for backend shknacluster03 with Vserver credentials.


2020-05-29 19:10:11.310 28 DEBUG manila.share.drivers.netapp.dataontap.cluster_mode.lib_base [req-7d2820bd-cff1-4318-88ca-3bae02c492f9 - - - - -] License info not available without cluster credentials _get_licenses /usr/lib/python2.7/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py:176


Additional info:
upstream queens backport attached.

Comment 20 errata-xmlrpc 2020-10-28 18:26:58 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 13 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4387