Skip to main content
NetApp Knowledge Base

Cinder volume creation fails due to NoValidBackend error at times

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

Applies to

  • OpenStack
  • Cinder
  • ONTAP 9

Issue

  • Cinder volume creation intermittently fails with NoValidBackend errors.
  • cinder-volume.log shows errors related to  storage service catalog updates:

cinder.volume.drivers.netapp.dataontap.utils.capabilities [-] Updating storage service catalog information for backend 'netapp'"
cinder.volume.drivers.netapp.dataontap.nfs_cmode [-] Address not found for NFS share XX.XX.XX.XX/vol1. 

cinder.volume.drivers.netapp.dataontap.nfs_cmode [-] Flexvol not found for NFS share XX.XX.XX.XX:/vol1.: cinder.exception.VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Could not find unique volume. Volumes found: [].

  • When failures occur, cinder get-pools does not list all storage backends.

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.