Trove-taskamager can't create volumes in different AZs

Bug #1395016 reported by Denis M. on 2014-11-21
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Morgan Jones

Bug Description

Trove-taskamager isn't able to create volumes in different AZs.

Cinder API allows to pass AZ as one of parameters on volume scheduling.

CLI view:
cinder help create
usage: cinder create [--snapshot-id <snapshot-id>]
                     [--source-volid <source-volid>] [--image-id <image-id>]
                     [--display-name <display-name>]
                     [--display-description <display-description>]
                     [--volume-type <volume-type>]
                     [--availability-zone <availability-zone>]
                     [--metadata [<key=value> [<key=value> ...]]]

Creates a volume.

Positional arguments:
  <size> Volume size, in GBs.

Optional arguments:
  --snapshot-id <snapshot-id>
                        Creates volume from snapshot ID. Default=None.
  --source-volid <source-volid>
                        Creates volume from volume ID. Default=None.
  --image-id <image-id>
                        Creates volume from image ID. Default=None.
  --display-name <display-name>
                        Volume name. Default=None.
  --display-description <display-description>
                        Volume description. Default=None.
  --volume-type <volume-type>
                        Volume type. Default=None.
  --availability-zone <availability-zone>
                        Availability zone for volume. Default=None.
  --metadata [<key=value> [<key=value> ...]]
                        Metadata key and value pairs. Default=None.

As you can see, '--availability_zone' can be passed through.

Here's some context:

We have couple AZs in one deployment: when booting Trove's instance we can pass --availability-zone. But when trying to attach volume to instance through block_mapping_device Nova tells that: Invalid volume: Instance and volume not in same availability_zone (HTTP 400)

Raizing bug priority to HIGH.

Denis M. (dmakogon) on 2014-11-21
summary: - Trove-taskamager isn't able to create volumes in different AZs
+ Trove-taskamager can't create volumes in different AZs
Denis M. (dmakogon) on 2014-11-21
description: updated
Changed in trove:
importance: Low → High
Denis M. (dmakogon) on 2015-01-20
Changed in trove:
assignee: nobody → Denis M. (dmakogon)

Fix proposed to branch: master

Changed in trove:
status: New → In Progress
Amrith Kumar (amrith) wrote :

It seems to be a contradiction to me that the importance of this bug is "High" yet the target is "Trove ongoing".

Change abandoned by Denis M. (<email address hidden>) on branch: master

Amrith Kumar (amrith) wrote :

Morgan, I'm assigning this to you since I see a BP proposal from you for this topic.

Changed in trove:
milestone: ongoing → newton-1
assignee: Denis M. (dmakogon) → nobody
status: In Progress → Triaged
assignee: nobody → Morgan Jones (6-morgan)
Amrith Kumar (amrith) on 2016-09-18
Changed in trove:
milestone: newton-1 → ongoing
Andy Botting (andybotting) wrote :

We have a similar setup as @Denis.M, and have been running with a similar patch for a while in production FWIW.

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

Other bug subscribers