rbd-mirror: Set the data pool correctly when creating images

Previously the data-pool option was ignored by rbd-mirror, so when using
erasure coding data for the image on the secondary site would end up in
the metadata pool.

Configure the data-pool using the data-pool's name from the primary site
when creating images on the secondary site.

Fixes: http://tracker.ceph.com/issues/20567

Signed-off-by: Adam Wolfe Gordon <awg@digitalocean.com>
(cherry picked from commit dffaac83d1)
This commit is contained in:
Adam Wolfe Gordon 2017-08-10 15:31:38 -04:00 committed by Jason Dillaman
parent cd50aad45a
commit 07e4b72680

View File

@ -74,6 +74,8 @@ void CreateImageRequest<I>::create_image() {
m_remote_image_ctx->stripe_unit);
image_options.set(RBD_IMAGE_OPTION_STRIPE_COUNT,
m_remote_image_ctx->stripe_count);
image_options.set(RBD_IMAGE_OPTION_DATA_POOL,
m_remote_image_ctx->data_ctx.get_pool_name());
librbd::image::CreateRequest<I> *req = librbd::image::CreateRequest<I>::create(
m_local_io_ctx, m_local_image_name, m_local_image_id,