juju not passing correct api version when attaching volumes in openstack

[Andre Ruiz]

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-xxx-version 2.60.

$ juju list-storage
<...>
      test-devices/39 block usc01-az01-abs-stable1 50GiB attaching failed to attach volume
caused by: request (https://acs.us-central-1.tcsecp.com:8774/v2.1/servers/ef1b5142-05f2-4103-9fed-2bafb68fd155/os-volume_attachments) returned unexpected status: 400; error info: {"badRequest": {"code": 400, "message": "Multiattach volumes are only supported starting with compute API version 2.60."}}
<...>

$ juju list-storage-pools
Name Provider Attributes
cinder cinder
loop loop
rootfs rootfs
tmpfs tmpfs
usc01-az01-abs-arbor cinder volume-type=usc01-az01-abs-arbor
usc01-az01-abs-stable1 cinder volume-type=usc01-az01-abs-stable1

$ openstack volume type show usc01-az01-abs-arbor
+--------------------+-----------------------------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------+-----------------------------------------------------------------------------------------------------------------+
| access_project_ids | None |
| description | None |
| id | 5e44595b-012c-41b3-a842-b8c1637a4000 |
| is_public | True |
| name | usc01-az01-abs-arbor |
| properties | RESKEY:availability_zones='us-central-1-az01', multiattach='<is> True', volume_backend_name='cinder-ceph-arbor' |
| qos_specs_id | 8ffaeb35-9016-483c-a674-dbbd0bf2e337 |
+--------------------+-----------------------------------------------------------------------------------------------------------------+

[Andre Ruiz (andre-ruiz)]

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.

[Vitaly Antonenko (anvial)]

Does this bug report still actual?

[Launchpad Janitor (janitor)]

[Expired for Canonical Juju because there has been no activity for 60 days.]

[Andre Ruiz (andre-ruiz)]

Unless this has already been fixed recently, this is still a valid bug and I see no reason for it to be marked incomplete and expired. I'm setting it back to New to be re-evaluated.

I don't have access to the environment where this occurred anymore, but I may be able to respond questions if any, and eventually set up a new env to replicate the problem if you can't.

[Joseph Phillips (manadart)]

The nova client in the goose library appears to have a hard-coded "v2" for use in constructing the service URL.

The ideal approach would be to request the versions and use the latest supported.

https://docs.openstack.org/api-ref/compute/?expanded=attach-a-volume-to-an-instance-detail,list-all-major-versions-detail#list-all-major-versions