microversion 1.1 not present

[Radosław Piliszek]

Running plain:

> openstack segment list

results in:

-----
A default microversion for service instance-ha of 1.1 was requested, but the cloud only supports a maximum of only supports a minimum of 1.0 and a maximum of 1.0. The default microversion was set because a microversion formatted version string, '1.1', was passed for the api_version of the service. If it was not intended to set a default microversion please remove anything other than an integer major version from the version setting for the service.
-----

Adding "--os-ha-api-version 1.0" fixes the above but it is ugly and confusing.

Obviously I did not request microversion 1.1 at any point.

Note also the wording looks wrong: "supports a maximum of only [WHAT?] supports a minimum of 1.0 and a maximum of 1.0."

[Florian Faltermeier (florianfa)]

It affects me, too. Same issue as above

Openstack version: victoria
Deployment: kolla-ansible (victoria)
python-masakariclient-6.1.1 (won't also work with python-masakariclient-6.2.1)

Florian

[Radosław Piliszek (yoctozepto)]

It seems the error message gets inserted by openstacksdk: https://opendev.org/openstack/openstacksdk/src/commit/eecefcf6e90d6ce92c032467f9e969a8f08bfac7/openstack/config/cloud_region.py#L783-L802

There is an issue in how urls are handled. I see lots of 4xx codes in debug logs.

@florianfa: Could you share how your Masakari endpoints are set up in Keystone?

From shell, run:

  openstack catalog list

attach the output replacing hostnames if necessary (if they are sensitive data).

[Radosław Piliszek (yoctozepto)]

Side note: the confusing text of the error message will get fixed via https://review.opendev.org/c/openstack/openstacksdk/+/777354

[Radosław Piliszek (yoctozepto)]

I tracked it down to the way that endpoints are configured.
If the endpoint is configured to the base URL, then the version detection "works", i.e., it does not hit this bug: https://bugs.launchpad.net/masakari/+bug/1685145
However, then Masakari reports it supports only 1.0, which is obviously wrong.
I love these anti-affinity bugs, my favs.

[Radosław Piliszek (yoctozepto)]

So using endpoint of / would trigger this bug (and not the other).
Using endpoint of /v1 or /v1/ or /v1/$(tenant_id)s or /v1/$(project_id)s would hit the other bug and avoid this one.

[Radosław Piliszek (yoctozepto)]

The fix is included in https://review.opendev.org/c/openstack/masakari/+/458793 (the fix for the other bug; because it would be failing otherwise).

[Radosław Piliszek (yoctozepto)]

Some testing: https://review.opendev.org/c/openstack/masakari/+/777937

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/masakari 11.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/masakari 8.1.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/masakari 9.1.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/masakari 10.0.2 release.