coverage: 78.687% (-0.05%) from 78.732%
when pulling e0b454d on kayrus:backport-aliases
into fe8ded1 on gophercloud:v2.

I can't imagine it breaking anyone's code, and I'm for having this fix in v2.

I would like to request considering a revert of this because of the regression in #3347.

The mess was initially introduced by upstream openstack developers, who decided to rename long established service types. Without this fix most of the automatic functional tests against the devstack will be broken.
You can use a workarond proposed in terraform-provider-openstack/terraform-provider-openstack#1848

P.S. I agree that this fix looks not quite well, since we could not expect that shared-file-system will be an alias to sharev1. But this was a compromise to keep the backward compatibility on the v2 branch. Feel free to suggest a better solution to hunt with the hounds.

Do you have a link to the relevant upstream change?

here is one https://gitea10.opendev.org:3081/openstack/manila/commit/27f01aaa7692614c2e72498418a85545a2aed512?style=split&whitespace=show-all&show-outdated=
see also https://specs.openstack.org/openstack/service-types-authority/
UPD: it seems we can set the service aliases in the version descending order. But we need to be sure that the original shared-file-system doesn't lead to the v1 API

UPD2: openstack/devstack@d7c3c0a the volumev3 endpoint was removed from devstack.