Unable to boot VM from volume snapshot if volume AZ is different from compute AZ

Bug #1564970 reported by Roman Sokolkov
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
MOS Cinder
MOS Cinder
MOS Cinder

Bug Description

I'm trying create VM from volume snapshot.

It fails because Volume availability zone differs from Compute availability zone.

We have SIGNLE Ceph cluster, which is default availability zone "nova" in Cinder.
For computes we have multiple availability zones (AZ1, AZ2).

Version: MOS 7.0 (Ceph for all, KVM, Neutron+VxLAN)

Steps to reproduce:
1) Deploy MOS7.0 with Ceph
2) Create host aggregate with availability zone AZ1 (or any name differ from "nova")
3) Create volume from image
4) Create volume snapshot
5) Try to create VM from volume snapshot

Actual result:
Error: Failed to perform requested operation on instance "new01-snap", the instance has an error status: Please try again later [Error: Build of instance 43027300-582c-4bbf-8280-bbd0b7a56c00 aborted: Failure prepping block device.].

Expected result:
VM successfully booted

Full nova-compute.log: https://paste.mirantis.net/show/ky4TnOOUvbBAQOLbRJCs/

Related discussion: https://openstack.nimeyo.com/55237/openstack-dev-cinder-nova-cinder-and-nova-availability-zones

summary: - Unable to VM from volume snapshot if volume AZ is different from compute
- AZ
+ Unable to boot VM from volume snapshot if volume AZ is different from
+ compute AZ
description: updated
tags: added: area-cinder area-nova
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Roman, so this was sort of expected behavior in Kilo (7.0) :(

There is a patch for Cinder to ease the pain when Cinder is used with Ceph - https://review.openstack.org/#/c/217857/ - it was merged to Liberty and effectively introduced a tiny feature (specifically, a new config option), which allows you to specify a fallback AZ.

Changes introducing new config options are generally not back ported to stable branches. And it won't help on its own - you still have to configure Cinder properly.

I'll let Cinder team comment on this, whether we should put this into a MU doe 7.0 or not.

Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Roman Podoliaka is absolutely right. I vote to not backport any new features or config options to previous releases. If it's a customer-found bug and customer wants a fix, we can provide them a custom package with update. But in general, we don't backport such patches to MOS.

Revision history for this message
Roman Sokolkov (rsokolkov) wrote :

Ok, thanks for link. Agree w/ comments above.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.