NetApp cannot create FlexGroup shares configuring dedup/compression

Bug #2036931 reported by Felipe Rodrigues
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
In Progress

Bug Description

When operating NetApp driver with FlexGroup shares, they cannot be provisioned with
dedup or compression being modified. Suppose the share comes with dedupe/compression enabled,
if the operator is requested disabled, the driver fails while changing it. The same problem
occurs if the share is disabled and the request is to be enabled.

The async client operations used by FlexGroup to manage dedup and compression are using wrongly the "send_request", it is not part more of the object "connection, it is now part of the "self". [1][2][3][4]


Steps to reproduce

A chronological list of steps which will help reproduce the issue you hit:
* Configure a NetApp backend with FlexGroup
* Create a share type with "netapp:dedup" as "False"
* Create a share on the FlexGroup pool with the previous type

Expected result
The share should be created without the dedup.

Actual result
The share is not created, failing during the disabling dedup operation.

Latest Manila version.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master

Changed in manila:
status: New → In Progress
Vida Haririan (vhariria)
tags: added: netapp share-groups
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.