[Fiware-lab-help] Emergency - Open Storage doesn't work

[Tomasz Rak]

Dear Fi-Ware experts, Dear IMPACT Team

We appeal to you with an urgent request for help, because unexpected
problem in the implementation of generic enabler Object Storage GE - FIWARE
Implementation prevents us from continuing to work on our project. We are
looking for a contact to every possible person who can give us a hint about
what we are doing wrong.

We need help in the implementation of OpenStack. We launched base instance,
where the module Object Storage is necessary and access to the API
endpoint, through which we will be able to manage files. Unfortunately, the
module still reports that the user is not authorized to perform the
operation, despite correct data for administration authorizing (eg.
keystone operations works).

Problem details are in txt file attached.

Instructions from which we started
http://docs.openstack.org/developer/devstack/guides/single-vm.html

The exact link to version we downloaded / installed:
git clone https://git.openstack.org/openstack-dev/devstack

Proxy server comes from official openstack docs:
http://docs.openstack.org/juno/install-guide/install/apt/content/swift-install-controller-node.html

Will there be someone who will help us to quickly solve the problem?
Without it are almost all our work is stopped - this is one of the key
things in our architecture.

Naturally, in accordance with the recommendation I've described on
http://stackoverflow.com/ this problem - this is the direct link:
http://stackoverflow.com/questions/29561074/fiware-object-storage-authorization-error

Our IT people are experienced. We try to put a lot of work in the solution,
but I still do not know which way to go.

Best regards, and thank You for Your support
Tomasz Rak
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150414/ded2046b/attachment.html>
-------------- next part --------------
Apr 10 00:10:10 hgl01cdn001 account-server: 127.0.0.1 - - [09/Apr/2015:22:10:10 +0000] "HEAD /sdb1/287/AUTH_e25b32a839764681b21916b7cc8f4b55" 404 - "HEADhttp://91.232.102.168:8080/v1/AUTH_e25b32a839764681b21916b7cc8f4b55" "txee17503fc75148e681a8e-005526f8c2" "proxy-server 6528" 0.0003 "-" 6627 -
Apr 10 00:10:10 hgl01cdn001 proxy-server: - - 09/Apr/2015/22/10/10 HEAD /v1/AUTH_e25b32a839764681b21916b7cc8f4b55 HTTP/1.0 204 - Swift - - - - txee17503fc75148e681a8e-005526f8c2 - 0.0042 RL - 1428617410.781399012 1428617410.785646915 -
Apr 10 00:10:10 hgl01cdn001 proxy-server: Identity server rejected authorization
Apr 10 00:10:10 hgl01cdn001 proxy-server: Identity response: {"error": {"message": "Invalid username or password (Disable debug mode to suppress these details.)", "code": 401, "title": "Unauthorized"}}
Apr 10 00:10:10 hgl01cdn001 proxy-server: Retrying validation
Apr 10 00:10:11 hgl01cdn001 proxy-server: Identity server rejected authorization
Apr 10 00:10:11 hgl01cdn001 proxy-server: Identity response: {"error": {"message": "Invalid username or password (Disable debug mode to suppress these details.)", "code": 401, "title": "Unauthorized"}}
Apr 10 00:10:11 hgl01cdn001 proxy-server: Authorization failed for token

$ swift stat
Account HEAD failed:http://91.232.102.168:8080/v1/AUTH_e25b32a839764681b21916b7cc8f4b55 401 Unauthorized.