From: Deepika Upadhyay Date: Wed, 26 May 2021 19:25:13 +0000 (+0530) Subject: nautilus: qa/upgrade: disable update_features test_notify with older client as lockowner X-Git-Tag: v14.2.22~31^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=b0fa231cc1152a89d83e81b19e83324db7b35301;p=ceph.git nautilus: qa/upgrade: disable update_features test_notify with older client as lockowner * with the recent support for async rbd operations from pacific+ when an older client(non async support) goes on upgrade, and simultaneously interacts with a newer client which expects the requests to be async, experiences hang; considering the return code for request completion to be acknowledgement for async request, which then keeps waiting for another acknowledgement of request completion. this if happens should be a rare only when lockowner is an old client and should be deferred if compatibility issues arises. * amend upgrade test workunits to use respective stable branches Signed-off-by: Deepika Upadhyay --- diff --git a/qa/suites/upgrade-clients/client-upgrade-nautilus-pacific/nautilus-client-x/rbd/3-workload/rbd_notification_tests.yaml b/qa/suites/upgrade-clients/client-upgrade-nautilus-pacific/nautilus-client-x/rbd/3-workload/rbd_notification_tests.yaml index 1ff0ab19634..7ad393a6a0e 100644 --- a/qa/suites/upgrade-clients/client-upgrade-nautilus-pacific/nautilus-client-x/rbd/3-workload/rbd_notification_tests.yaml +++ b/qa/suites/upgrade-clients/client-upgrade-nautilus-pacific/nautilus-client-x/rbd/3-workload/rbd_notification_tests.yaml @@ -8,12 +8,13 @@ tasks: env: RBD_FEATURES: "61" - workunit: - branch: octopus + branch: pacific clients: client.1: - rbd/notify_slave.sh env: RBD_FEATURES: "61" + RBD_DISABLE_UPDATE_FEATURES: "1" - print: "**** done rbd: old librbd -> new librbd" - parallel: - workunit: