[NetApp] Check last-transfer size and error for replica state

Bug #1989175 reported by kiran pawar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
kiran pawar

Bug Description

On NetApp backend,
1] We need to consider last-transfer-size and last-transfer-error from snapmirror to find out replica is out_sync or in_sync.
2] User can configure the limit above which any value of last-transfer-size is considered as replica is out_of_sync.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/manila/+/856756

Changed in manila:
status: New → In Progress
Changed in manila:
importance: Undecided → Medium
assignee: nobody → kiran pawar (kpdev)
milestone: none → zed-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.opendev.org/c/openstack/manila/+/856756
Committed: https://opendev.org/openstack/manila/commit/6e8ed59a91934096a4ddc9b184ef50a633cbd1ec
Submitter: "Zuul (22348)"
Branch: master

commit 6e8ed59a91934096a4ddc9b184ef50a633cbd1ec
Author: Kiran Pawar <email address hidden>
Date: Fri Sep 9 11:31:34 2022 +0000

    [NetApp] Consider last transfer size and error for replica state

    In order to determine replica state from snapmirror, in addition to
    existing check of last-transfer-end-timestamp', also add new checks
    of `last-transfer-size` and `last-transfer-error`. New config option
    `netapp_snapmirror_last_transfer_size_limit` added with default value
    of 1MB. The last-transfer-size above this value or presence of any
    last-transfer-error is considered as replica is out_of_sync.

    Closes-bug: #1989175
    Change-Id: I6d038244493583cc943063b50d731b8c1ef5ed28

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 15.0.0.0rc1

This issue was fixed in the openstack/manila 15.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.