Comment 1 for bug 1098564

Interesting issue; let try to explain what's going on and how to work around it.

First, to delete and endpoint created with endpoint-create you should be using endpoint-delete, not service-delete:

  keystone endpoint-delete 410de5fed7544c90a36ebdb8b38f0cea

However, that's still going to fail in your case because you have an invalid endpoint in the catalog, so the client is failing to authenticate itself -- it's never getting as far as attempting to delete anything.

As a workaround, bypass authentication (the credentials specified by your environment variables) using token/endpoint values:

  keystone --os-token=<keystone.conf's admin_token> and --os-endpoint=http://localhost:35357/v2.0/ endpoint-delete 410de5fed7544c90a36ebdb8b38f0cea

Although this technically counts as user-error, I'd vastly prefer to see invalid endpoints suppressed from the service catalog output instead of raising an error back to the API and killing the authentication process. The current error message raised to the API should instead be logged to ERROR.