Skip to main content
NetApp Knowledge Base

Cinder Data Volume Attachment Fails with HTTP 400 Error in OpenStack Using NetApp ONTAP

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

Applies to

  • OpenStack Cinder with NetApp ONTAP iSCSI backend
  • Cinder Volume Attachments
  • RedHat OpenStack Services (RHOSO-18)

Issue

Some Cinder data volumes fail to attach in OpenStack, returning an HTTP 400 error. The issue is intermittent—some volume attachments succeed, while others fail.
Sample log output from cinder-volume:

2025-09-21 18:54:48.892608145 DEBUG cinder.volume.drivers.netapp.dataontap.block_base [...] Created LUN with name volume-9d1431c4-5c37-44d2-85a7-26ff61bc6dae [...]
2025-09-21 18:54:48.899608145 INFO cinder.volume.flows.manager.create_volume [...] Volume volume-9d1431c4-5c37-44d2-85a7-26ff61bc6dae created successfully
...
Some volume attachments return HTTP 400 errors.

 

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.