wrong endpoint for swift in a multi node setup when using CONFIG_STORAGE_HOST

Bug #1453269 reported by Christian Berendt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
New
Undecided
Ivan Chavero (imcsk8)

Bug Description

With rdo-testing-kilo it is not possible to use swift in a multi node setup when using CONFIG_STORAGE_HOST.

The endpoint URLs are pointing to 10.100.50.10 (this is the CONFIG_CONTROLLER_HOST), but the swift-proxy-server process is running on 10.100.50.40 (this is the CONFIG_STORAGE_HOST).

$ openstack endpoint show 5249273fd9754a4b9f696d2e9cfb3d8c
+--------------+----------------------------------+
| Field | Value |
+--------------+----------------------------------+
| adminurl | http://10.100.50.10:8080 |
| enabled | True |
| id | 5249273fd9754a4b9f696d2e9cfb3d8c |
| internalurl | http://10.100.50.10:8080 |
| publicurl | http://10.100.50.10:8080 |
| region | RegionOne |
| service_id | 8e209b4fc26e4ed4856892af619ab463 |
| service_name | swift_s3 |
| service_type | s3 |
+--------------+----------------------------------+

Changed in packstack:
assignee: nobody → Ivan Chavero (imcsk8) (ichavero-ichavero)
Revision history for this message
Alan Pevec (apevec) wrote :

Ivan, did you have a WIP fix for this?

Revision history for this message
Alan Pevec (apevec) wrote :

Quickfix could be to force CONFIG_STORAGE_HOST=CONFIG_CONTROLLER_HOST ?

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.