juju not passing correct api version when attaching volumes in openstack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I have a juju controller in openstack. I also have a few storage-pools which volume-types have multiattach property enabled in openstack.
When deploying a new app with extra storage from those pools, juju is not passing API 2.60 in the call and attachment does not happen.
Volumes from these volume-types do work well when attached via openstack CLI but I *do* have to specify --os-api-
$ juju list-storage
<...>
test-
caused by: request (https:/
<...>
$ juju list-storage-pools
Name Provider Attributes
cinder cinder
loop loop
rootfs rootfs
tmpfs tmpfs
usc01-az01-
usc01-az01-
$ openstack volume type show usc01-az01-
+------
| Field | Value |
+------
| access_project_ids | None |
| description | None |
| id | 5e44595b-
| is_public | True |
| name | usc01-az01-
| properties | RESKEY:
| qos_specs_id | 8ffaeb35-
+------
tags: | added: op storage |
tags: |
added: api openstack-provider removed: op |
Changed in juju: | |
importance: | Undecided → Low |
status: | New → Triaged |
Just to make sure nothing else is a problem, I just created a new volume-type similar to the existing one but without multiattach, and then the volumes are created and attached nicely.