Skip to main content
NetApp Knowledge Base

Unable to Extend OpenStack Cinder Volume Size After LUN Move on NetApp ONTAP Backend

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

Applies to

  • OpenStack Cinder with NetApp ONTAP backend (ONTAP 9.x, e.g., 9.14.1P6)
  • NetApp All SAN Array (ASA) platforms
  • Environments where LUNs are managed by OpenStack Cinder and NetApp storage

Issue

After moving a LUN from one NetApp volume to another directly on the ONTAP backend (outside of OpenStack), attempts to extend the corresponding OpenStack Cinder volume from the OpenStack layer fail. The volume goes into an error state.

Example log output / symptom:

  • OpenStack Cinder volume extension fails with error state after LUN move
  • No failed resize operations seen on ONTAP for the original volume
  • Cinder logs may reference “VolumeBackendAPIException” or inability to find the LUN

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.