RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Trying to delete source file system with cloned file system on NetApp target leads to plugin bug:
PLUGIN_BUG(2): Volume 'NAME' cannot be destroyed because it has clone volumes (vendor error code= 15894) 

sim target has slightly different message:
PLUGIN_BUG(2): Requested file system is a clone source

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

How reproducible:
100%

Steps to Reproduce:
1. create file system (lsmcli fs-create)
2. clone file system (lsmcli fs-clone)
3. try to delete source file system (lsmcli fs-delete)

Actual results:
PLUGIN_BUG(2): Volume 'NAME' cannot be destroyed because it has clone volumes (vendor error code= 15894)

Expected results:
warning / delete file system

Additional info:

By design, if specified fs is a replication source, you cannot delete it.
The problem here are:
 * Need a dedicate error number in libstoragemgmt for refusing delete on 
   replication source volume/fs.
 * Need treat NetApp EOP_DISALLOWED_ON_CLONE_PARENT/15894 error as this new
   introduced libstoragmegmt error number.

Patch has been submitted to upstream for review:
https://github.com/libstorage/libstoragemgmt/pull/315

SIM:
# lsmcli -u "sim://" fs-delete --fs='FS_ID_00001'
Warning: You are about to do an operation that will cause data to be lost!
Press [Y|y] to continue, any other key to abort
HAS_CHILD_DEPENDENCY(161): Requested file system has child dependency

ONTAP:
# lsmcli  -u "ontap://user@target" fs-delete --fs='b27bc241-c30a-46cf-99b9-23e5bc8434ab'
Warning: You are about to do an operation that will cause data to be lost!
Press [Y|y] to continue, any other key to abort
HAS_CHILD_DEPENDENCY(161): Specified file system has child dependency (is source of clone)

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, 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/RHEA-2018:0864