Latency requirement for sanlock = write 1MB with bs=512 odirect=yes within 10s
Providing the qa_ack for this bug, as this feature is MUST for forthcoming release
https://github.com/gluster/gluster-ansible-features/pull/26/commits/b07e55c99b PR: https://github.com/gluster/gluster-ansible-features/pull/26
Tested the bug with gluster-ansible-features-1.0.5-1 . The validation check is added. Steps: ===== 1.Start the gluster deployment 2.Check for the below validation Snippet: ======= 2019-05-28 11:58:34,018 p=23364 u=root | TASK [gluster.features/roles/gluster_hci : Check the disk latency (mount points)] *** 2019-05-28 11:58:41,358 p=23364 u=root | changed: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:58:41,660 p=23364 u=root | changed: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:58:42,360 p=23364 u=root | changed: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:58:48,895 p=23364 u=root | changed: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:58:50,692 p=23364 u=root | changed: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:58:50,964 p=23364 u=root | changed: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:58:58,113 p=23364 u=root | changed: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore) 2019-05-28 11:58:59,595 p=23364 u=root | changed: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore) 2019-05-28 11:59:00,011 p=23364 u=root | changed: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore) 2019-05-28 11:59:00,150 p=23364 u=root | TASK [gluster.features/roles/gluster_hci : Check if time taken to copy 1M file (512B chunks) is < 10s] *** 2019-05-28 11:59:00,310 p=23364 u=root | skipping: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=4.07206) 2019-05-28 11:59:00,311 p=23364 u=root | skipping: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=4.33922) 2019-05-28 11:59:00,312 p=23364 u=root | skipping: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=4.55125) 2019-05-28 11:59:00,463 p=23364 u=root | skipping: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=2.96322) 2019-05-28 11:59:00,464 p=23364 u=root | skipping: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=3.27225) 2019-05-28 11:59:00,465 p=23364 u=root | skipping: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=6.48417) 2019-05-28 11:59:00,491 p=23364 u=root | skipping: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=2.73093) 2019-05-28 11:59:00,502 p=23364 u=root | skipping: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=4.83074) 2019-05-28 11:59:00,513 p=23364 u=root | skipping: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=3.00159) 2019-05-28 11:59:00,653 p=23364 u=root | TASK [gluster.features/roles/gluster_hci : Unmount the volume] ***************** 2019-05-28 11:59:04,921 p=23364 u=root | changed: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:59:04,966 p=23364 u=root | ok: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:59:05,099 p=23364 u=root | ok: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/engine) 2019-05-28 11:59:09,142 p=23364 u=root | changed: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:59:09,144 p=23364 u=root | ok: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:59:09,254 p=23364 u=root | ok: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/data) 2019-05-28 11:59:13,364 p=23364 u=root | changed: [rhsqa-grafton8.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore) 2019-05-28 11:59:13,367 p=23364 u=root | ok: [rhsqa-grafton9.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore) 2019-05-28 11:59:13,446 p=23364 u=root | ok: [rhsqa-grafton7.lab.eng.blr.redhat.com] => (item=/mnt/tmp/vmstore)
https://github.com/gluster/gluster-ansible-features/pull/32 fixes the issue.
Verified the bug with gluster-ansible-features-1.0.5-3.el7rhgs.noarch The disk latency check is removed. So moving the bug to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2557