-
Story
-
Resolution: Obsolete
-
Normal
-
None
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
-
As a cloud operator, i want service objects in Keystone to be automatically removed or recognized by the Keystone operator during Adoption, so that i don't have to delete them manually.
Currently Keystone adoption steps contain this:
openstack service list | grep ' cinderv3 ' | awk '{ print $2; }' | xargs openstack service delete || true openstack service list | grep ' glance ' | awk '{ print $2; }' | xargs openstack service delete || true openstack service list | grep ' neutron ' | awk '{ print $2; }' | xargs openstack service delete || true openstack service list | grep ' nova ' | awk '{ print $2; }' | xargs openstack service delete || true openstack service list | grep ' placement ' | awk '{ print $2; }' | xargs openstack service delete || true openstack service list | grep ' swift ' | awk '{ print $2; }' | xargs openstack service delete || true
It would be good if this deletion would be performed automatically by the Keystone operator, or even better if the operator recognized these service entries and used them. Currently if these aren't cleaned up, KeystoneService CRs creation conflicts with them and gets stuck.
- is cloned by
-
-
- Closed
-
