Skip to main content
NetApp Knowledge Base

LUN Mapping Not Restored After Snapshot Revert in OpenStack Cinder with NetApp ONTAP

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

Applies to

  • NetApp ONTAP 9.16.1P10 (and similar ONTAP versions)
  • OpenStack Cinder (Z release)
  • Lenovo DM7200F (AFF OEM)
  • Fibre Channel (FC) and iSCSI environments
  • Boot/system (root) volumes in OpenStack
  • Lenovo xCloud or similar OpenStack orchestration frameworks

Issue

After performing a “revert to snapshot” operation on a boot/system volume in an OpenStack-integrated environment using NetApp ONTAP as the backend, the LUN mapping is not automatically restored. This results in the volume becoming inaccessible to the original VM/host until manual intervention is performed.

Observed behavior:

  • The original LUN is unmapped and destroyed during the revert process.
  • A new cloned LUN is created from the snapshot.
  • The new LUN is not mapped to the original host/igroup.
  • All paths in multipath show as failed.
  • Manual mapping is required to restore access.
  • Issue is reproducible across all boot volumes; data volumes are not affected.

Relevant log output:

[ONTAP audit logs]
Unmapping LUN volume-7757d269-f469-49e3-807f-fcc8902a7ad9 from the initiators ['initiator,'initiator'] terminate_connection_fc
...
Volume 7757d269-f469-49e3-807f-fcc8902a7ad9 reverted to snapshot successfully.
...
After snapshot restore, the LUN is in unmapped state, but manual mapping can be performed successfully.

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.