LookupError: Entry point 'gatekeeper' not found in egg 'swift'
This bug report was converted into a question: question #243513: LookupError: Entry point 'gatekeeper' not found in egg 'swift'.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi, after update to latest version (1.12.0), proxy not runing:
root@proxy:
Starting proxy-server.
Traceback (most recent call last):
File "/usr/bin/
run_
File "/usr/lib/
loadapp(
File "/usr/lib/
ctx = loadcontext(
File "/usr/lib/
global_
File "/usr/lib/
global_
File "/usr/lib/
return loader.
File "/usr/lib/
object_type, name=name, global_
File "/usr/lib/
global_
File "/usr/lib/
for name in pipeline[:-1]]
File "/usr/lib/
object_type, name=name, global_
File "/usr/lib/
section)
File "/usr/lib/
object_type, name=use, global_
File "/usr/lib/
object_type, name=name, global_
File "/usr/lib/
global_
File "/usr/lib/
global_
File "/usr/lib/
return loader.
File "/usr/lib/
object_type, name=name)
File "/usr/lib/
for prot in protocol_options] or '(no entry points)'))))
LookupError: Entry point 'gatekeeper' not found in egg 'swift' (dir: /usr/lib/
Middlewares:
root@proxy:
account_quotas.py bulk.py cname_lookup.py container_sync.py domain_remap.py gatekeeper.py __init__.py list_endpoints.py name_check.py ratelimit.py slo.py tempauth.py
acl.py catch_errors.py container_quotas.py crossdomain.py formpost.py healthcheck.py keystoneauth.py memcache.py proxy_logging.py recon.py staticweb.py tempurl.py
I do not understand where is problem, hepl please
Changed in swift: | |
status: | New → Invalid |
i hate setuptools so much and continue to blame pbr for everything that goes wrong.
What linux distribution (version) are you installing on?
How do you install swift (pre-built package, build your own)?
I so desperately wish that someone could just understand this failure mode and explain to me WHAT is broken rather than "after running some random set of setuptools/pip/apt commands that other people mentioned when they ran into this same problem - IT WORKED!"