Openstack Keystone : 'Client' object has no attribute 'service_catalog'

When I try the following command on my setup
keystone catalog
or
keystone token-get
I get the following error

'Client' object has no attribute 'service_catalog'
When I run in debug mode I can see that the issue is client side.
I checked my environment variables
env | grep --perl "^OS|^SERV"
the variables SERVICE_ENDPOINT and SERVICE_TOKEN were defined and taking precedence

Doing following resolved it
export SERVICE_TOKEN=

export SERVICE_ENDPOINT= 

Comments

  1. Hi Abhisar,

    I'm having the same problem also with those variables in my environment.
    here below the exported variables.
    Could you please make a check with your successful installation to help me to solve the problem?
    thanks million
    danilo

    if you want you can write at apecar67 at gmail dot com

    CONTROLLER_INTERNAL_ADDRESS=nube.virt
    CONTROLLER_PUBLIC_ADDRESS=nube.virt
    MAIL=/var/mail/root
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    PWD=/root
    OS_PASSWORD=password
    LANG=en_US.UTF-8
    OS_AUTH_URL=http://nube.virt:35357/v2.0
    OS_USERNAME=admin
    SHLVL=1
    HOME=/root
    LANGUAGE=en_US:en
    OS_TENANT_NAME=demo
    LOGNAME=root
    SERVICE_ENDPOINT=http://nube.virt:35357/v2.0
    LESSOPEN=| /usr/bin/lesspipe %s
    SERVICE_TOKEN=012345SECRET99TOKEN012345
    ADMIN_PASSWORD=password
    LESSCLOSE=/usr/bin/lesspipe %s %s
    ENABLE_QUANTUM=Yes

    ReplyDelete
    Replies
    1. Hi Danilo,
      Sorry for being late.
      If you make the variables SERVICE_ENDPOINT and SERVICE_TOKEN empty, it should work.
      Use below commands
      export SERVICE_TOKEN=
      export SERVICE_ENDPOINT=

      Delete
    2. THANKS FOR THIS! I had been racking my brain for this solution, Sorry to dredge up a year old post, but THANKS!

      Delete
  2. Thanks a lot..it works..:)

    ReplyDelete

Post a Comment

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]