swift: Inconsistent output on endpoint configuration

Bug #997186 reported by Marco CONSONNI
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
High
Anne Gentle

Bug Description

I defined swift endpoint as described here http://docs.openstack.org/trunk/openstack-compute/install/content/keystone-service-endpoint-create.html (near sentence "Define the Object Storage service").

I noticed that the second command output (command "keystone -... endpoint-create") is not consistent with the values of the submitted parameters.

In fact the output reads as follows:

+-------------+----------------------------------------------------------------+
| Property | Value |
+-------------+----------------------------------------------------------------+
| adminurl | http://127.0.0.1:8080/ |
| id | e32b3c4780e51332f9c128a8c208a5a4 |
| internalurl | http://192.168.206.130:8080 |
| publicurl | http://127.0.0.1:8080/v1/AUTH_eb7e0c10a99446cfa14c244374549e9d |
| region | RegionOne |
| service_id | 272efad2d1234376cbb911c1e5a5a6ed |
+-------------+----------------------------------------------------------------+

We have the following problems:

1) public URL is "resolved" in the sense that tenant_id is reported as hexadecimal value whilst the output you get is not resolved

2) internal URL does not contain "v1/AUTH_%(tenant_id)s" as submitted in the command and the address is not the one submitted

----

In addition to this "exclusively formal" discrepancy, I'm not sure port 8080 is correct, I presume the right port should be 8888 as configured in /etc/swift/proxy-servere.conf described here http://docs.openstack.org/trunk/openstack-compute/install/content/installing-and-configuring-the-proxy-node.html.
If this is true, this is a genuine documentation bug more urgent to fix.
Unfortunately I was not able to verify this theory about port 8888 because when I submit the command for verifying reported here http://docs.openstack.org/trunk/openstack-compute/install/content/verify-swift-installation.html (command swift -V 2 ...), I get the following error:

Auth GET failed: http://10.15.8.18:5000/v2.0/tokens 401 Not Authorized

Please verify.

---

In conclusion, the former problem (output discrepancy) is a minor problem, the latter (port number) could be a more serious problem.

Revision history for this message
Anne Gentle (annegentle) wrote :

I think this is a true doc bug. Adding Chmouel to get his input.

Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Marco CONSONNI (marco-consonni) wrote :

Hello,

let me add some information on this topic.

I found out that the right port number to indicate in the endpoint is 8888 or, to be more precise, it must be the same value in /etc/swift/proxy-conf.conf.

Related to this bug, see also this https://bugs.launchpad.net/openstack-manuals/+bug/997446.

There are problems on swift-proxy configuration: it seems like some code is "unreachable".
As far as I understand, the code is downloaded but, for some mysterious reason, is unreachable (see ma latest post).

Revision history for this message
Marco CONSONNI (marco-consonni) wrote :

Sorry, I was forgetting a further important comment.

In the related bug I mentioned (https://bugs.launchpad.net/openstack-manuals/+bug/997446), I reported some other indications for fixing other documentation bugs.

See my post starting with "Good.".

As you will see, swift command reported here http://docs.openstack.org/trunk/openstack-compute/install/content/verify-swift-installation.html, need to be fixed.

Hope it helps.

Anne Gentle (annegentle)
Changed in openstack-manuals:
assignee: nobody → Anne Gentle (annegentle)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/7362

Changed in openstack-manuals:
status: Confirmed → In Progress
Revision history for this message
Anne Gentle (annegentle) wrote :

Please review https://review.openstack.org/7362 to see if it at least fixes the 8888/8080 problem. Still not sure what you mean by "resolved" in "1) public URL is "resolved" in the sense that tenant_id is reported as hexadecimal value whilst the output you get is not resolved" - more input appreciated. :)

Revision history for this message
Marco CONSONNI (marco-consonni) wrote :

I checked.

Not being sure if I was supposed to do some action on the review pages, I'm reporting my comments here.

The change in the input parameter from 8080 to 8888 is fine.

Still we have a minor problem in the command output that should read as follows:

+-------------+----------------------------------------------------------------+
| Property | Value |
+-------------+----------------------------------------------------------------+
| adminurl | http://127.0.0.1:8888/ |
| id | e32b3c4780e51332f9c128a8c208a5a4 |
| internalurl | http://127.0.0.1:8888/v1/AUTH_%(tenant_id)s |
| publicurl | http://127.0.0.1:8888/v1/AUTH_%(tenant_id)s |
| region | RegionOne |
| service_id | 272efad2d1234376cbb911c1e5a5a6ed |
+-------------+----------------------------------------------------------------+

Note that URLs read exactly as you typed in the command.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/7362
Committed: http://github.com/openstack/openstack-manuals/commit/97a490b9ed843b217cde7e61b225d697ece080f5
Submitter: Jenkins
Branch: master

commit 97a490b9ed843b217cde7e61b225d697ece080f5
Author: annegentle <email address hidden>
Date: Fri May 11 16:57:05 2012 -0500

    Fix bug 997446, bug 997186

    - Fixes endpoint in endpoint creation command to match the swift proxy.conf file.
    - Fixes swift CLI verification commands - tenant:user not user:password.

    Change-Id: I9cf555c9f814499499a8c23da58c290b1b6de9a5

Changed in openstack-manuals:
status: In Progress → Fix Committed
Anne Gentle (annegentle)
Changed in openstack-manuals:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.