OpenStack Object Storage (swift)

swift container-sync not working

Asked by Netmagic Solutions

Hi,

We are running two separate clusters of swift 1.5.0 with swauth 1.0.6.

We are trying to set up container sync between accounts on both the cluster, but getting below error on container server on one of the clusters :

May 15 16:35:42 Zone4-S001 container-sync Unauth 'AUTH_25d97b67-134c-49a5-bf61-194047787d1f/container1' => 'https://simplidrivenoi.netmagicsolutions.com/v1/AUTH_fcecf343-f35f-423a-bfae-e8200d3f6293/container2'

We have configured below parameters on all the storage nodes (no configuration done on proxy servers) :

1) in container-server.conf file :
under [DEFAULT] section
allowed_sync_hosts = 127.0.0.1,180.179.199.181,simplidrivenoi.netmagicsolutions.com

under [container-sync] section :
log_name = container-sync
log_level = DEBUG

Is there anything we are missing here ?

Regards,

Viral Patadiya

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Object Storage (swift) Edit question
Assignee:
No assignee Edit question
Solved by:
dimm
Solved:
Last query:
Last reply:
Revision history for this message
John Dickinson (notmyname) said : 		#1

That looks correct for configuration, but the log line you are seeing is from swauth. Looking at the code, it's hard to tell exactly what's causing it (it's a catch-all log line). One possibility is that your clusters clocks are out of sync.

Revision history for this message
Netmagic Solutions (simplidrive) said : 		#2

Hi,

The clocks are already in sync. Even the sync is not happening between two accounts in the same cluster.

couple of queries :

1. Is it because we have a LB with ssl in front of proxies ?
2. Is it mandatory to have storage nodes on public IPs? We just have public IPs for the sake of management, otherwise the storage segment is on private IPs only.
3. have tried syncing two containers from two different account on the same cluster, even that is not happening.

Any more ideas ?

Regards,

Viral

Revision history for this message
Best dimm (dmitry-pha) said : 		#3

Just solved the same problem.

In proxy-server.conf [filter:swauth] section I had the hostname specified in allowed_sync_hosts, while the system was expecting IP address

Revision history for this message
Netmagic Solutions (simplidrive) said : 		#4

Thanks dimm, that solved my question.