Red Hat Bugzilla – Bug 1472859
keystone catalog should not have entries for disabled api (cinder v1)
Last modified: 2017-07-21 08:21:08 EDT
Description of problem:
enable_v1_api defaults to false in the /etc/cinder/cinder.conf
however the keystone catalog still has an v1 endpoint for cinder.
Version-Release number of selected component (if applicable):
The keystone catalog does not have not follow-able link.
python-tempestconf is trying to list the available extensions when it it sees it in the catalog.
The devstack gate does not likes the idea:
ATM not a good idea to just remove it.