Trove-taskamager can't create volumes in different AZs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Triaged
|
High
|
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>]
Creates a volume.
Positional arguments:
<size> Volume size, in GBs.
Optional arguments:
--snapshot-id <snapshot-id>
--source-volid <source-volid>
--image-id <image-id>
--display-name <display-name>
--display-
--volume-type <volume-type>
--availabilit
--metadata [<key=value> [<key=value> ...]]
As you can see, '--availability
Here's some context:
We have couple AZs in one deployment: when booting Trove's instance we can pass --availability-
Raizing bug priority to HIGH.
summary: |
- Trove-taskamager isn't able to create volumes in different AZs + Trove-taskamager can't create volumes in different AZs |
description: | updated |
Changed in trove: | |
importance: | Low → High |
Changed in trove: | |
assignee: | nobody → Denis M. (dmakogon) |
Changed in trove: | |
milestone: | newton-1 → ongoing |
Fix proposed to branch: master /review. openstack. org/148563
Review: https:/