osdsctl Replication stuck at creating

[daramosch]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug /kind feature

What happened:

Create 2 LVM Pools from 2 Different VGs which used IBM SVC and the Other Uses infinibox. I was able to create volumes, xfs format them and mount it to the OS from the Volume ID on osdsctl.

However when I tried to create replication between them they get stuck at creating status which does not allow me to do anything beyond that point. osdsctl replication delete / enable failed with message "ERROR: Can't delete the replication in creating"

Debug shows OK Message: [root@~]# osdsctl replication list --debug DEBUG: 2019/05/08 11:48:59 receiver.go:110: GET http://[myip]:50040/v1beta/e93b4c0934da416eb9c8d120c5d04d96/block/replications/detail?sortDir=desc&limit=50&offset=0&sortKey=id DEBUG: 2019/05/08 11:48:59 receiver.go:136: StatusCode: 200 OK Response Body: [{"id":"63432400-129a-433f-9207-7c6a29c7a057","createdAt":"2019-05-08T11:34:01","updatedAt":"","tenantId":"e93b4c0934da416eb9c8d120c5d04d96","primaryVolumeId":"c8e0e543-9ab1-47cb-ba34-2d676ab4f6d7","secondaryVolumeId":"58756109-3297-4fdc-a28c-9f9e907eb039","replicationStatus":"creating","replicationMode":"async","replicationPeriod":60},{"id":"ff0d5cc9-5766-45e4-aa86-67b1359f2e43","createdAt":"2019-05-08T11:16:57","updatedAt":"2019-05-08T11:25:05","tenantId":"e93b4c0934da416eb9c8d120c5d04d96","primaryVolumeId":"e7905e6f-9742-4c1d-a6ba-1020e7c184e7","secondaryVolumeId":"0d8ad4c9-22cf-4e54-a332-f49aaf337899","replicationStatus":"creating","replicationMode":"sync"}] +--------------------------------------+------+-------------+--------------------------------------+--------------------------------------+------------------+-------------------+-----------------+ | Id | Name | Description | PrimaryVolumeId | SecondaryVolumeId | AvailabilityZone | ReplicationStatus | ReplicationMode | +--------------------------------------+------+-------------+--------------------------------------+--------------------------------------+------------------+-------------------+-----------------+ | 63432400-129a-433f-9207-7c6a29c7a057 | | | c8e0e543-9ab1-47cb-ba34-2d676ab4f6d7 | 58756109-3297-4fdc-a28c-9f9e907eb039 | | creating | async | | ff0d5cc9-5766-45e4-aa86-67b1359f2e43 | | | e7905e6f-9742-4c1d-a6ba-1020e7c184e7 | 0d8ad4c9-22cf-4e54-a332-f49aaf337899 | | creating | sync | +--------------------------------------+------+-------------+--------------------------------------+--------------------------------------+------------------+-------------------+-----------------+

What you expected to happen:

Been able to kick off replication between volumes on different pools

How to reproduce it (as minimally and precisely as possible):

Create 2 Pools on LVM.yaml from different Storage Arrays. Create Volumes on each pool, format xfs, mount and create a replication, error seems to repeat either with sync or async Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:0.5.1
• OS (e.g. from /etc/os-release):

NAME="Red Hat Enterprise Linux Server" VERSION="7.6 (Maipo)" ID="rhel" ID_LIKE="fedora" VERSION_ID="7.6" PRETTY_NAME="Red Hat Enterprise Linux Server 7.6" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:server" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.6 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION=7.6

• Kernel (e.g. uname -a): Linux amdc-stg-lx02 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Jan 30 11:00:34 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

• Install tools: Manual installation

• Others:

[xing-yang]

It looks like you have passed the installation issue reported here: https://github.com/opensds/opensds/issues/719?

So I assume you are trying to do host-based replication? Have you installed DRBD on your servers?

[daramosch]

This is a different Environment this is an installation on Redhat while #719 is with Ubuntu

[skdwriting]

@kumarashit please check and reply/ close, thank you.

[leonwanghui]

@daramosch I think this issue has been fixed by #853, please take a test, thanks

[skdwriting]

@daramosch , could you please verify and confirm the same.