There is no object-store endpoint on this auth server

Asked by dubi

I have run stack.sh for a devstack gitted (master).
swift is not enabled so nova-objectstore should be active . keystone seems to work ok since curl gives the token
in return for the admin/passw0rd credentials.

Yet when running : swift -A http://9.148.4.71:5000/v2.0 -U admin -K passw0rd list

I get back : " There is no object-store endpoint on this auth server"

any idea why ?

actually there were intallation where it did not happen , but I don't see any diff between them

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Identity (keystone) Edit question
Assignee:
No assignee Edit question
Solved by:
dubi
Solved:
Last query:
Last reply:
Revision history for this message
dubi (dubi-il) said :
#1

solved

Revision history for this message
Jean-Pierre Dion (jean-pierre-dion) said :
#2

Hi,
how did you solve this ? I am facing the same issue.

Thank you.

jean-pierre

Revision history for this message
dubi (dubi-il) said :
#3

actuall I did not solve it directly but made some change (enabled minimal local swift instead of nova-objectstore ) and it worked
I did not come back to the nova-objectstore usage . But in the meanwhile I learned more and think the above error message might come from the fact that keystone was not active ( do : 'ps _ax | grep keystone' to see if you have keystone-all running) . if so run :
python /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf

to start keystone ( should be in that path if .devstack/install.sh finished ok)

Now here is how I activated swift (minimal configuration) instead of nova-objectstore :

1) run : uninstal.sh to revert the old intallation and then : rm -fr /opt/stack/*
then copy /devstack/samples/localrc (a swift install example) to devstack directory with some changes as follows (including some passwords of your own . mine were all : 'passw0rd') :

# Minimal Contents
# ----------------

# While ``stack.sh`` is happy to run without ``localrc``, devlife is better when
# there are a few minimal variables set:

# If the ``*_PASSWORD`` variables are not set here you will be prompted to enter
# values for them by ``stack.sh``.
ADMIN_PASSWORD=passw0rd # my passwords!!
MYSQL_PASSWORD=passw0rd
RABBIT_PASSWORD=passw0rd
SERVICE_PASSWORD=$ADMIN_PASSWORD

# HOST_IP should be set manually for best results. It is auto-detected during the
# first run of ``stack.sh`` but often is indeterminate on later runs due to the IP
# being moved from an Ethernet interface to a bridge on the host. Setting it here
# also makes it available for ``openrc`` to include when setting ``OS_AUTH_URL``.
# ``HOST_IP`` is not set by default.
HOST_IP=9.148.4.71

# Set DevStack Install Directory
# ------------------------------

# The DevStack install directory is set by the ``DEST`` variable. By setting it
# early in ``localrc`` you can reference it in later variables. The default value
# is ``/opt/stack``. It can be useful to set it even though it is not changed from
# the default value.
DEST=/opt/stack

# Swift
# -----

# Swift is now used as the back-end for the S3-like object store. If Nova's
# objectstore (``n-obj`` in ``ENABLED_SERVICES``) is enabled, it will NOT
# run if Swift is enabled. Setting the hash value is required and you will
# be prompted for it if Swift is enabled so just set it to something already:
SWIFT_HASH=66a3d6b56c1f479c8b4e70ab5c2000f5
# following we request only key. mysql and swift modules . No nova or else
ENABLED_SERVICES=key,mysql,swift

# For development purposes the default of 3 replicas is usually not required.
# Set this to 1 to save some resources:
SWIFT_REPLICAS=1

# The data for Swift is stored in the source tree by default (``$DEST/swift/data``)
# and can be moved by setting ``SWIFT_DATA_DIR``. The directory will be created
# if it does not exist.
SWIFT_DATA_DIR=$DEST/data

2) Install again by running : /devstac/install.sh and enter any passwords prompted for .
3) when install finishes ok run : /devstack /source opnerc
4) now start swift like this: swift-init all start ( to later stop swift (if you need ) do : swift-init all stop.
    it should finish ok but if there is any error message like bind problem to port 8080 search for the application
    using that port and stop it or rerun the app with a different port than 8080 because I have found that swift likes to use
   8080 without change . to find out how ports are used in the system run as root: netstat -ntpl

5) To test the installed swift run: devstack/exercises/swift.sh . it should finish ok with NO failures on the way

6) make your tests of swift like :
     swift stat (or : swift -A http:<you Ip>:5000/v2.0/ -U <user> -K <password> stat)
     swift post <container name >
     swift upload <container> <file>
     swift list <container>
     swift downlaod <file> -o <outputfile>
     swift delete <container > <file>

   generally type: swift<ret> to get swift help