Use of versioned endpoint for cinder v3 causes issues on upgrade

[Giulio Fidente]

It looks like we're creating some new endpoints in 16.1 because not only the service *name* is set to "cinderv3" but the service *type* as well, hence it doesn't refresh the existing service type (which is set to "cinder") but rather creates some new ones:

| 029ea458062140d9ae4f4ccd2c9766db | regionOne | cinderv3 | volumev3 | True | internal | http://10.20.0.18:8776/v3/%(tenant_id)s
| 0b5de1e471b543209321c5e46619b823 | regionOne | cinderv2 | volumev2 | True | public | http://10.1.0.100:8776/v2/%(tenant_id)s
| 0fd68734f3b84090a64c9fb29b8aa492 | regionOne | cinderv3 | volume | True | internal | http://10.20.0.18:8776/v3/%(tenant_id)s
| 13d39a29f87c417ca395845b197c53bf | regionOne | cinderv3 | volumev3 | True | public | http://10.1.0.100:8776/v3/%(tenant_id)s
| 367120213b2a47bb9ed005c1de66d4e2 | regionOne | cinderv2 | volumev2 | True | admin | http://10.20.0.18:8776/v2/%(tenant_id)s
| 82d860dafce74fe28986b64be5d58702 | regionOne | cinderv3 | volume | True | public | http://10.1.0.100:8776/v3/%(tenant_id)s
| a9a4333bffcf450f9bc0df3576675972 | regionOne | cinderv2 | volumev2 | True | internal | http://10.20.0.18:8776/v2/%(tenant_id)s
| bf9c18b1e1174662bc7bb2f9af32e3c7 | regionOne | cinderv3 | volumev3 | True | admin | http://10.20.0.18:8776/v3/%(tenant_id)s
| db31919f88274cf2b7a8a37280720bc3 | regionOne | cinderv3 | volume | True | admin | http://10.20.0.18:8776/v3/%(tenant_id)s

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/739451

[Alan Bishop (alan-bishop)]

I think this LP misstates the actual problem. I filed another LP (and associated patch to fix it), which I feel contains a more accurate problem description. See these:

https://launchpad.net/bugs/1897761
https://review.opendev.org/755070

[OpenStack Infra (hudson-openstack)]

Change abandoned by Giulio Fidente (<email address hidden>) on branch: master
Review: https://review.opendev.org/739451
Reason: not the right fix; rather have the external scripts deal with the possibility of multiple services for volume*