Multi-site sync failed when buckets uses not default placement in source zone

Hi, @Yehuda Sadeh-Weinraub <yehuda(a)redhat.com> @Casey Bodley <cbodley(a)redhat.com> @Matt Benjamin <mbenjamin(a)redhat.com> and Cephers We met a problem with the Elastic Search sync module: bucket with custom placement could not be synced to the target zone. The target zone tries to create a bucket instance based on the placement name, but the target zone does have the placement. logs as following: meta sync: ERROR: can't store key: bucket.instance: * data sync: ERROR: failed to fetch bucket instance info for * ERROR: select_bucket_placement() returned -22 we are going to fix this issue. here are some questions: 1. should we sync those buckets to the ES zone? it seems not necessary 2. should we sync placements? if we sync placements to the target zone, we also need to create rados pools in the target zone thanks Chang Liu