OSC 7.0.0: quota set needs both compute and volume

[Dr. Jens Harbott]

command: openstack --debug quota set --instances 40 $project

expected result (working with <7): quota getting set successfully

current result: internal endpoint for block-storage service in RegionOne region not found

this happens when nova is deployed without cinder or vice-versa when trying to set volume quota. both are valid deployment scenarios. the commit that causes this seems to be https://opendev.org/openstack/python-openstackclient/commit/70fbf687cf10e67d1e05120b15533725f106a1f6

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/python-openstackclient/+/925861
Committed: https://opendev.org/openstack/python-openstackclient/commit/6693f555bcc412bc84226bb71d093e77a2ab240c
Submitter: "Zuul (22348)"
Branch: master

commit 6693f555bcc412bc84226bb71d093e77a2ab240c
Author: Stephen Finucane <email address hidden>
Date: Wed Aug 7 12:44:37 2024 +0100

    quota: Allow 'quota set' to function without volume service

    Unlike cinderclient, SDK attempts to connect to a service as soon as you
    create a client. A keystoneauth1.exceptions.catalog.EndpointNotFound
    exception can be raised if this service does not exist in the service
    catalog. Avoid this for the quota and limits commands by first checking
    if the service is enabled.

    In the process, we rework the 'is_volume_endpoint_enabled' helper we are
    using to check for the existence of the service to *not* require a
    volume client, since this was causing a chicken and egg issue for us
    (and was also pretty much unnecessary).

    Change-Id: I56e68f00ea221d689eb7f668e9e5ffa7d1a20184
    Signed-off-by: Stephen Finucane <email address hidden>
    Closes-bug: #2076229

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-openstackclient 7.1.0 release.